WIP: Automatically close Git for Windows' milestones after a release #67
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a work in progress! The idea is that as part of closing a `[New git release]` ticket that is associated with a Git for Windows release, we will close the current milestone and open the next one. The current work-in-progress script was used to successfully close the v2.44.0 milestone and open the `Next release` one. So what's missing? This: - The current script needs to be replaced by a proper route in `index.js` - More validations are needed, so that we do not close, say, a milestone that does not even have any issues assigned to it. Or a milestone that is for another version. - Tests. This will address git-for-windows#7. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
|
I opened this because I have no idea when I'll be able to work on this, if ever. Read: If anyone is interested in running with this, I'd be happy! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a work in progress! The idea is that as part of closing a
[New git release]ticket that is associated with a Git for Windows release, we will close the current milestone and open the next one. The current work-in-progress script was used to successfully close the v2.44.0 milestone and open theNext releaseone. So what's missing? This:The current script needs to be replaced by a proper route in
index.jsMore validations are needed, so that we do not close, say, a milestone that does not even have any issues assigned to it. Or a milestone that is for another version.
Tests.
This will address
#7.