Skip to content

Conversation

@dscho
Copy link
Member

@dscho dscho commented Nov 5, 2025

Over the years, a lot of the functionality in that monster of a Unix shell script has been moved and/or reimplemented elsewhere. It's time to clean up.

dscho added 9 commits November 3, 2025 10:05
It has been removed from Git for Windows, and even before that, it was
unsupported for several years.

Signed-off-by: Johannes Schindelin <[email protected]>
We used to upgrade packages using a single command, but that did not
integrate well with GitHub Actions. Therefore we now have the system
where the `monitor-components.yml` workflow monitors for new versions,
opening new tickets if there are, the `/open pr` commands can be used in
those tickets to open Pull Requests in MINGW-packages, MSYS2-packages or
build-extra, and the `/add release-note` command can then update the
release notes.

Therefore we do not need that old shell function anymore.

Signed-off-by: Johannes Schindelin <[email protected]>
This function was used to prepare the release notes and the announcement
mail in the Azure Pipelines in which Git for Windows was released.

However, nowadays this task is performed elsewhere, specifically
https://github.com/git-for-windows/git-for-windows-automation/blob/main/update-scripts/tag-git.sh

For that reason, we do not need to carry this function anymore.

Signed-off-by: Johannes Schindelin <[email protected]>
This logic was used in Azure Pipelines to finalize the release notes
before releasing new Git for Windows versions.

These days, that job is performed elsewhere, specifically in
https://github.com/git-for-windows/git-for-windows-automation/blob/56d8604016d6/update-scripts/tag-git.sh#L55-L62

So let's retire that function (and some support functions, too).

Signed-off-by: Johannes Schindelin <[email protected]>
These packages are no longer built using `please.sh`, but using scripts
contained in
https://github.com/git-for-windows/git-for-windows-automation.

Signed-off-by: Johannes Schindelin <[email protected]>
The Coverity stuff now lives in upstream Git's `coverity.yml` workflow.

Signed-off-by: Johannes Schindelin <[email protected]>
This was used in the release process that has migrated completely to
git-for-windows-automation, and in the Coverity stuff (which has moved
to upstream Git anyway).

Signed-off-by: Johannes Schindelin <[email protected]>
The process to upstream `mingw-w64-git` to the MSYS2 project will have
to be done very, very differently now.

Signed-off-by: Johannes Schindelin <[email protected]>
@dscho dscho requested review from mjcheetham and rimrul November 5, 2025 10:53
@dscho dscho self-assigned this Nov 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants