Do not run "Check required jobs" on forks #470
Merged
Conversation
This file contains 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
jgiannuzzi
force-pushed
the
required-checks-no-fork
branch
from
d20da23
to
92ee4e7
Compare
dsuhinin
approved these changes
Oct 17, 2023
This was referenced Oct 18, 2023
suprjinx
pushed a commit
to suprjinx/fasttrackml
that referenced
this pull request
Oct 23, 2023
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.
#458 introduced the use of a GitHub environment and a GitHub app to implement the required checks. On repo forks, these will most likely not exist, and the need for any kind of required checks is probably close to zero.
This PR is thus disabling the required checks creations on forks.