ci: add workflow to notify maintainers on fork PRs not running integration tests#3211
Merged
Conversation
julian-risch
approved these changes
Apr 24, 2026
Member
julian-risch
left a comment
julian-risch
left a comment
There was a problem hiding this comment.
Looks good to me! Only checking out the base branch SHA (the trusted target branch), not head.sha (the fork's code). Further ${{ steps.affected.outputs.list }} can only contain known integration names, no other content.
marocchino/sticky-pull-request-comment is a GitHub action that we're not using anywhere else yet. Looks good to me. They enabled immutable releases on GitHub two weeks ago, which is good. Still, let's keep in mind that another GitHub action means an additional risk and we could for example fork the action.
Member
Author
|
It works. See #3234 |
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.
Related Issues
We don't expose secrets on PRs from forks for security reasons.
This also means that integration tests are skipped if API keys are required. In these cases, the maintainer should run the tests locally before merging the PR.
Proposed Changes:
How did you test it?
Hard to test. I'll test when merged and fix if not working properly.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:.