@joachim It's a good technique as it works (and allows for quick side-tracks to other branches without losing progress or losing sight of where you are in your thought process) ;-)
My local branches are generally called "WIP/feature/whatever-the-real-branch-will-be-called", so after the clean up, I just remove the "WIP" before pushing it and submitting the PR.
(I always work via PRs, even when I'm the only contributor to a project)
@skc I'll most likely do a soft reset and then do a new commit with all the changes in it.
The reason why I do it like that, is that it allows me to review and double-check my changes while staging and to describe all the changes in the commit message while viewing them.
Squash does not give me access to the changed code for a final check.
@3v4l Sorry to bother you again, but figured you'd want to know: the latest PHP 8.2 and 8.3 versions are not running and show the following error:
> Warning: PHP Startup: Unable to load dynamic library 'sodium.so' (tried: /usr/lib/php/8.3.5/modules/sodium.so (libsodium.so.23: cannot open shared object file: No such file or directory), /usr/lib/php/8.3.5/modules/sodium.so.so (/usr/lib/php/8.3.5/modules/sodium.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
These versions provide compatibility hotfixes to continue to allow for running tests using a PHPUnit PHAR file after today's PHPUnit 8.5.38, 9.6.19 and 10.5.17 releases.
When you receive my replies to the #PHP internals mailing list, do they look empty to you? I just noticed that my messages on both news.php.net and externals.io appear empty.
@heiglandreas@ramsey LOL... been seeing that so often... especially with newsletters/mailing lists.
Apparently people use "Create new from" a lot and only update the HTML. When you receive the email and view it in plain text, the content doesn't match and often is about something completely different...
Case in point: all the emails from #DPC24... (the text version is the original announcement that they're back in person and that the CfP is open,)
⚠️ Please note that this release - even though only pushed as a patch release - contains a very minor BC break. Please check the release notes for more details.
@3v4l Hiya, would it be possible to update the PHP master for 3v4l ?
Looks like the current version is from end of Januari and would be nice to check the behaviour of some of the deprecations which have been merged for PHP 8.4 since then.
@redcrew Interesting. I'd been looking at that and was curious why nobody had mentioned it so far.
The one thing I'm hesitant about is the 5 tag limit in the free version as that sounds very very limiting. Also feels like a bit of a lock-in as the export options seem limited as well (in the free version) and buying a Pro version to leave doesn't sound right to me.