Alerta! Alerta!
Antifascist! Father. Husband. PHP-Nerd. Draughtsman. Soil-Scientist. Kayaker. Rescue-Diver. OSS-Maintainer. Challenge-Accepter.
Homebase roughly 50N 8E
@ teamup.com, ingewikkeld.net & stella-maris.solutions
There is no “unpolitical”
- 3 Posts
- 23 Comments
@phpstorm And then I have to open the worktree as a new Project in a separate window? I can’t attach it to the current project?
🤯
And even opening it in the same window will create a totally separate .idea folder and all my settings from before are … gone…
Whoever thought that’s a good UX might want to reconsider that decision…
@phpstorm It’s me. And also my #edgecases
When you create a worktree inside a container and didn’T set
git config worktree.useRelativePaths truethen thegitdiffile in the.git/worktreefolder and the.gitfile in your visible worktree will link to each other in absolute paths - based on the containers filesystem…Outside the container PHPStorm can then not find those files and 💥
Thanks for the learning opportunity! 🙈
Oh and the submodules were stuck in
.idea/vcs.xml…
Alerta! Alerta!@phpc.socialto
Programming@chrastecky.dev•Transpiling PHP for older versions
11·2 years ago@dominik Have you thought of using build-numbers instead of (ab)using the patch number?
x.y.z+84
x.y.z+83
etc…But my biggest concern is actually security or size-related. 'Cause how do I provide the data to packagist? I either need separate repositories for those ehich increases the maintenance burden or requires sophisticated automization. Or I provide precompiled “binaries” - which can contain anything. Even code that is not in the repo - a security nightmare…
How did you solve that?
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
2·2 years ago@BatmanAoD so far I have seen more issue-trackes come and go than VCSs…
So yes: Training developers in commit-discipline would for me not be wasted time and money.
Cause from what I have seen so far the question is not *whether* the issue tracker changes but *when*.
But OTOH: That’s just me (and some companies I worked at).
YMMV
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years ago@BatmanAoD Whatever tool people are using for their issues and/or PRs and/or VCS
And it’s not about trusting the tool but trusting that the tool will always be available. Whether due to discontinuation of the tool itself or due to discontinued use of the tool and replacement by something else…
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years ago@BatmanAoD Oh I am absolutely with you that commit messages document the development history.
And there are valid cases for code-comments (I am a strong proponent of them) when they explain why something is solved in this specific way that would otherwise cause confusion when reading the code! But those tend to suffer from entropy 😁
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years ago@BatmanAoD It all depends on the maturity of the toolchain… and the longtime availablility of the external dependencies 😁
And. I no longer trust them further than I can spit… 🙈
But YMMV 😁
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
2·2 years ago@BatmanAoD And the commit message *is* documentation. It explains the “Why” making transparent why the code was written the way it is. If the commit message doesn’T reflect that, then you can also use
git commit -m "Fixed issues"But again: That is then a people problem that no tech will solve!
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years ago@BatmanAoD Because the commit message is a requirement when committing code. The code comment is sitting there and no one cares whether it’S updated.
And a certain schema of a commit message can be enforced. Git hooks for example can be used to make sure that the commit message looks a certain way, has a minimum length, is formatted according to declared standards. As one would do for code-style.
Then they still can just add garbage. But then you have a people problem that no tech will solve
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
2·2 years ago@BatmanAoD And every developer should take the time to create a meaningful commit-message for the work they did. After all they invested a good amount of time into the code change, so why not proudly explain why they did it, what the challenges where and why they did it
*that* way?But on the other hand: It’s documentation, so just drop it 🙈
Also: Code-comments are fine but tend to rot during code changes. The commit message is always tied to the commit.
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
2·2 years ago@BatmanAoD Having done code archeology for over a decade now I can assure you that the issue with all the information that you need to understand why something was done has been discarded just shortly before due to moving to a different platform… Or something similar.
In any case: Having all the relevant data in one place and not scattered is a huge advantage.
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years ago@clovis They already DO support it.
/cc @ramsey @jetbrains
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years agoWhether the users then use conventional commits, beams rule, opensavvy, whatever else they want is a completely different question.
And I am absolutely with you that Jetbrains should not favour one over the other.
/cc @ramsey @jetbrains
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
1·2 years agoWe might be talking about two different sets of standard. What I would want Jetbrains to support out of the box is the “Subject line, Blank Line, Body” convention that is recommended in the git docs.
People can happily change the defaults to whatever they want but the recommendation from git should IMO be the default.
/cc @ramsey @jetbrains
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
41·2 years ago@Cyno IIRC I explicitly talked about the Jetbrains UI.
Others I didn’t check and mean! Sorry if it came across like that!
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
3·2 years ago@BatmanAoD Besides that a git log and a changelog have different target audiences.
The gitlog is intended for contributors of the project whereas the chamgelog is intended for users of the project.
And it helps the users if they get a summarized version of what changed for them.without having to.go.theough each commit amd decide for themselves whether and how that internal change affects the exteenal API and then their usage of it.
Alerta! Alerta!@phpc.socialOPto
JetBrains@programming.dev•After seeing people use the UI to commit to git I understand where all those - sorry: shitty - commit messages come from....
4·2 years ago@Xitnelat Indeed. But software can help.
After all an email editor also has different fields for different content, while it is perfectly possible to write an email.with a texteditor.
And while everything is possible, the “Subject line, empty line, Body (empty line, trailer)” is what it’s intended to be.
So why not help the person in front of the monitor with that…
/cc @jetbrains


@schnurrito When PHP admins have work to do, that means that they didn’T do their homework.
PHP releases security updates in a regular interval. Setting up an automated process of pulling those (once the patches actually have reached a distro - most admins will not use the patches directly) in should have been done already.
And when the work is “trigger the update script” then that isn’t work.
The most tedious work will be “Is the patch compiled yet?” checking…