We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Whoops, forgot to adjust some parts the the new lay of the land.
Adjust the documentation to how things are done now using the GitForWindowsHelper GitHub App
Releasing Git for Windows: we do push to `main` more quickly, nowadays Signed-off-by: Johannes Schindelin <[email protected]>
Releasing Git for Windows: note that Pacman takes a long time Folks who did the release for the first time indicated to be surprised by this ;-) Signed-off-by: Johannes Schindelin <[email protected]>
Releasing Git for Windows: link to the "new git version" issue Signed-off-by: Johannes Schindelin <[email protected]>
Releasing Git for Windows: We no longer use `git-sdk-*-extra-artifacts` The Pipelines generating the extra artifacts were historically used to generate Git for Windows' release artifacts, but we cut that out and now have a much faster, much more streamlined release process. Signed-off-by: Johannes Schindelin <[email protected]>
We just switched from an Azure Pipeline synchronizing the git-sdk-* repositories to two GitHub workflows
Releasing Git for Windows: describe a convenient alias Let's automate All The Things! Signed-off-by: Johannes Schindelin <[email protected]>
Releasing Git for Windows: fix scriptlet It is quite possible that there are no upstreamed commits between two upstream Git tags, e.g. between -rc versions. For those, the indicated scriptlet would generate an empty `sed` script. Let's handle that case appropriately. Signed-off-by: Johannes Schindelin <[email protected]>
Fix whitespace issues Signed-off-by: Johannes Schindelin <[email protected]>
Releasing Git for Windows: explain how to integrate last-minute changes outside of Git's own source code Signed-off-by: Johannes Schindelin <[email protected]>
At long last, taking some time to write all of this down