You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tag-git/git-artifacts: allow tagging and building MinGit backports
In the past, I built MinGit backports by crafting tags manually, then
letting an Azure Pipeline pick that tag up, automatically determine the
corresponding `mingit-2.<N>.x-releases` release branch name, and then
build the MinGit assets.
However, with the nice `tag-git` and `git-artifacts` GitHub workflows
already doing much of what is needed to streamline the process, we can
easily adjust both workflows to allow ticking a `mingit-only` checkbox
and use the exact same flow for MinGit backports as for embargoed Git
for Windows releases: open a PR with the changes, start the `tag-git`
workflow, and once it finishes, kick off corresponding `git-artifacts`
workflow runs, one for each supported architecture.
The main adjustment is this `mingit-only` checkbox, writing the
`mingit-only` file to the `bundle-artifacts` artifact if set, and
crafting slightly a different release notes/tag title than regular Git
for Windows releases'.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
0 commit comments