Migrate release management to GitHub projects v2 #305
Merged
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
Zimmi48
force-pushed
the
migrate-projectV2
branch
3 times, most recently
from
e55878d to
41a01e3
Compare
Even if this is not supposed to be allowed.
Fix coq#303 by removing the use of this part of the API.
Zimmi48
force-pushed
the
migrate-projectV2
branch
6 times, most recently
from
ecb3de1 to
d697e09
Compare
Zimmi48
force-pushed
the
migrate-projectV2
branch
from
d697e09 to
78d0175
Compare
|
I have now fixed the issues I discovered this morning. I will merge this pull request to avoid staying longer with a deployment which is not from the main branch. I will address the remaining todos (documentation and auto-creating views) later. |
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.
Partially implements #278 (
without removing the project V1 support, so that we can test this while keeping the other one for now). What is missing:@proux01 @silene I intend to test-deploy this, so https://github.com/orgs/coq/projects/11/views/4 and https://github.com/coq/coq/projects/42 should in principle be updated concurrently when new PRs are merged or backported in the 8.20+rc1 milestone.
Close coq/coq#19156.
Close #278.
Close #303.