Repository navigation
feat: post repository security advisories - #19
Merged
Merged
Conversation
Add a repository_advisory event that posts only the GHSA ID, title, severity and link, so a scheduled workflow can announce unpublished advisories. New optional event and payload-path inputs let a workflow pass advisories in, one message per payload in the file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 of 6 tasks
reitblatt
marked this pull request as ready for review
November 3, 2026 21:18
Advisory titles are written by reporters and can reveal the vulnerability, so post the GHSA ID, state, severity and link only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cassidyjames
reviewed
Nov 3, 2026
cassidyjames
left a comment
Member
There was a problem hiding this comment.
Some nits/feedback but nothing blocking
| WEBHOOK: ${{ inputs.webhook-url }} | ||
| run: | | ||
| if [ ! -s "$RUNNER_TEMP/discord.json" ]; then | ||
| echo "Skipping: draft or bot pull request" |
Member
There was a problem hiding this comment.
nit:
Suggested change
| echo "Skipping: draft or bot pull request, or no advisories" |
Comment on lines
+43
to
+44
| # Stay under Discord's webhook rate limit when posting several | ||
| $first || sleep 1 |
Member
There was a problem hiding this comment.
This is prooooobably fine, though I wonder if we should increase the sleep to give ourselves some wiggle room. I looked up the Discord webhook rate limit and their official recommendation is to parse response headers in case of rate limiting which seems… a lot more complex for this use case.
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
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.
Extends the bot to add support for repository security advisory events, so Coop (roostorg/coop#1523) and later Osprey can announce newly reported or drafted advisories in a private security channel.
GitHub Actions has no advisory event, so when using this action, you will need to create a scheduled workflow to list the new advisories and pass them in. See the above coop PR for an example of how to do this.
Testing