Only run 'Deploy' action on main repository #3200
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
Deploy action will always fail on forks as the token is not there.
justinmayer
approved these changes
Oct 4, 2023
There was a problem hiding this comment.
Thanks for the enhancement, @lioman. I wish it were possible to globally disable a GitHub Action job from running on any fork without having to specify the origin org+repository name explicitly, but that doesn't seem possible. There is a pre-existing discussion thread about precisely that topic, to which I posted a comment with my own suggestions.
For now, I think explicitly naming "getpelican/pelican", as is done here, is the only way to do it, so we might as well use that method until a better solution comes along.
|
Just researched it, and I was kind of surprised, that there is no easier/cleaner solution then this. |
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.
Deploy action will always fail on forks as the token is not there, this happens on the fork especially, when you are syncing with, main one. This will improve the setup for collaborators.