Skip to content

Adapt to renamed release notes files #607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2025

Conversation

orgads
Copy link
Contributor

@orgads orgads commented Mar 18, 2025

@orgads
Copy link
Contributor Author

orgads commented Mar 18, 2025

@dscho Should also update in the published 2.49 release notes.

@dscho
Copy link
Member

dscho commented Mar 18, 2025

Oy. As if there had not been enough fall-out from that ill-thought-through rename.

Thank you @orgads!

@dscho dscho merged commit 29108a5 into git-for-windows:main Mar 18, 2025
6 checks passed
@orgads orgads deleted the relnotes-adoc branch March 18, 2025 15:03
dscho added a commit to git-for-windows/git-for-windows-automation that referenced this pull request Mar 18, 2025
This is the gazillionth follow-up to that rename; It was noticed in
git-for-windows/build-extra#607 that this needed
yet another adjustement, this time in Git for Windows' release notes. In
that PR, the `please.sh` script was adjusted, which indeed used to be
how the release notes generation was automated.

In the meantime, we have moved from an Azure Pipelines-based
automation to a GitHub Actions-based automation, and the `please.sh`
script is no longer used to generate those; Instead the
`update-scripts/tag-git.sh` script in this here repository is used for
that purpose.

Therefore, the latter script needs to be adjusted, too.

Signed-off-by: Johannes Schindelin <[email protected]>
dscho added a commit to git-for-windows/git-for-windows-automation that referenced this pull request Mar 18, 2025
This is the gazillionth follow-up to that rename; It was noticed in
git-for-windows/build-extra#607 that this needed
yet another adjustement, this time in Git for Windows' release notes. In
that PR, the `please.sh` script was adjusted, which indeed used to be
how the release notes generation was automated.

In the meantime, we have moved from an Azure Pipelines-based
automation to a GitHub Actions-based automation, and the `please.sh`
script is no longer used to generate those; Instead the
`update-scripts/tag-git.sh` script in this here repository is used for
that purpose.

Therefore, the latter script needs to be adjusted, too.

Signed-off-by: Johannes Schindelin <[email protected]>
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