Pull Request Automation: Avoid automation tasks for forked repository#20021
Merged
Pull Request Automation: Avoid automation tasks for forked repository#20021
Conversation
Member
Author
See https://github.com/WordPress/gutenberg/runs/424412032?check_suite_focus=true |
talldan
approved these changes
Feb 4, 2020
Contributor
talldan
left a comment
There was a problem hiding this comment.
Looks good! Thanks for tackling it so swiftly.
Contributor
|
The action was skipped successfully here: https://github.com/WordPress/gutenberg/pull/20025/checks |
Member
Author
|
@talldan That's great! It occurs to me, looking at the log, there are two things we can improve:
I created #20031 for tracking. |
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.
Related: #17324
This pull request seeks to avoid running automation tasks for pull request events when the event was triggered by a pull request originated from a forked repository. Based on the comment at #17324 (comment), events which trigger from forked repositories are run with read-only permissions, and as such are not allowed to add labels, resulting in errors for tasks which perform these actions.
Testing Instructions:
The actions associated with this pull request should be expected to run fully and successfully, since it does not originate from a fork repository.