Post internals + blog PR after publishing dev-static releases #45
Conversation
This file contains hidden or 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 automatically opens an internals thread and a blog PR after promoting a stable release (if configured, and will only be configured on dev-static). Caveat: needs human user to set release notes URL and scheduled release date. That will be done via flags to start-release.py in simpleinfra, probably.
Mark-Simulacrum
force-pushed
the
dev-blog
branch
from
7fb1d54 to
37d33fd
Compare
This was referenced Jul 15, 2022
Merged
pietroalbini
approved these changes
Jul 16, 2022
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.
Tested locally -- see https://internals.rust-lang.org/t/rust-1-62-0-pre-release-testing-v2/16983 (may need admin credentials) and Mark-Simulacrum/blog.rust-lang.org#8 for the sample PRs opened by this.
I think the PR being opened vs. directly pushing makes sense, but we could consider altering that in the future, once this is proven to work.