Improve the descriptions of PRs created by the release process #1254
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
aeisenberg
approved these changes
Sep 16, 2022
This was referenced Sep 21, 2022
This was referenced Jun 22, 2023
This was referenced Nov 30, 2023
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.
Recommend removing and then re-adding the "Update dependencies" label when appropriate to avoid having to run the full set of PR checks twice. This isn't a completely satisfying solution but should reduce friction before we implement something that updates the dependencies without requiring an additional triggering step.
Recommend marking the PR as ready for review to avoid having to close and reopen the PR to run checks.
Avoid duplicating the PR titles like this:
Instead, just link the PR and let GitHub format the title nicely.
Merge / deployment checklist