feat(release-review-pr): add findings-collector checklist item - #429
Open
hdamker wants to merge 1 commit into
Open
feat(release-review-pr): add findings-collector checklist item#429hdamker wants to merge 1 commit into
hdamker wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What type of PR is this?
enhancement/feature
What this PR does / why we need it:
Adds a Release Management Actions checklist item to the Release Review PR template: content findings needing a
mainPR get collected as sub-issues of one issue titledRelease {{release_tag}} review findings, linking to the convention's documentation. Includes a regression-test assertion covering the new line.Which issue(s) this PR fixes:
Part of camaraproject/ReleaseManagement#650
Special notes for reviewers:
A companion PR in
camaraproject/ReleaseManagementdocuments the convention this checklist item links to. Wording here is a starting point for discussion per ReleaseManagement#650, not final text to defend.