Add script to ping PR authors and issue reporters after a release - #329
Open
wallrj-cyberark wants to merge 2 commits into
Open
Add script to ping PR authors and issue reporters after a release#329wallrj-cyberark wants to merge 2 commits into
wallrj-cyberark wants to merge 2 commits into
Conversation
hack/ping-release-prs.sh checks each given PR number to see whether a ping comment referencing the release tag URL has already been posted (using per_page=100 to avoid missing comments on long threads). If not, it posts a brief comment on the PR and on any linked closing issues, skipping self-reported issues automatically. The script is idempotent and supports --dry-run. Signed-off-by: Richard Wall <[email protected]>
cert-manager-prow
Bot
added
the
dco-signoff: yes
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
cert-manager-prow
Bot
added
the
size/L
…rted issues For a patch release the release notes list the cherry-pick PRs. Those have no linked issues and are authored by the bot, so the script commented on the cherry-pick and pinged nobody. It now follows "cherry-pick of #N" in the PR body to the original PR, so the pings land where the contributor and reporter are watching. The comment said "pre-release" whatever the release was. It now says "pre-release" or "release" to match the GitHub release, and the lookup fails early if the tag does not exist. Issues reported by a member of the repository's organization are skipped, as self-reported issues already were. Maintainers know about the release. Co-Authored-By: Claude Fable 5.1 <[email protected]> Signed-off-by: Richard Wall <[email protected]>
This was referenced Sep 11, 2026
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
2 participants
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 does this do?
Adds
hack/ping-release-prs.sh. After a release is published, it posts a comment on each included PR telling the author the change is available, and a comment on each issue those PRs close asking the reporter to verify the fix.It is idempotent. It skips any PR or issue that already has a comment linking to the release, and it reads 100 comments per page so a long thread does not hide an earlier ping.
Why
How it works
For each PR number given:
The wording says "pre-release" or "release" to match the GitHub release, and the lookup fails early if the tag does not exist.
Usage
Requires
gh(authenticated) andjq.Dry run for v1.21.2
14 PR comments and 3 issue comments would be posted.
A website PR adds this as a step in the release process.
[Claude Fable 5.1]