Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(.github): Add release verification prompts to PR template section "Upgrade Considerations" #10444

Merged
merged 3 commits into from
Nov 26, 2024
Merged

chore(.github): Add release verification prompts to PR template section "Upgrade Considerations" #10444

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
11ddfbd
chore(.github): Add "Release Verification" to the PR template
gibson042 Nov 11, 2024
efce9a3
chore(.github): Incorporate the new prompts into Upgrade Considerations
gibson042 Nov 11, 2024
e7ee0d2
Merge branch 'master' into gibson-2024-11-release-verification
mergify[bot] Nov 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,4 +32,4 @@ refs: #XXXX
<!-- Every PR should of course come with tests of its own functionality. What additional tests are still needed beyond those unit tests? How does this affect CI, other test automation, or the testnet? -->

### Upgrade Considerations
<!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? -->
<!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? What steps should be followed to verify that its changes have been included in a release (ollinet/emerynet/mainnet/etc.) and work successfully there? If the process is elaborate, consider adding a script to scripts/verification/. -->
Loading