-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip Build and Deploy jobs on forks instead of failing them #153
base: main
Are you sure you want to change the base?
Conversation
I like this addition, with more 'meta' changes like this I'll wait till Isaac provides feedback though. Otherwise I approve! |
.github/workflows/mdbook.yml
Outdated
@@ -16,6 +16,7 @@ concurrency: | |||
|
|||
jobs: | |||
build: | |||
if: github.repository == 'Whisky-App/whisky-book' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should just be skipping the deployment step and not the build step. It's still valuable to make sure that build is working as intended on forks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have tried it but it fails on my fork always at least.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skip the setup pages step, but not the entire job
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No? You can just disable them in your repository’s actions…
This is the output of a conditional applied to the Build job:
|
Description
Type(s)
Verification
Have you
./scripts/generate.mjs
?./scripts/lint.mjs
?This PR addresses an issue where a push to a forked repo causes error and a notification with such on GitHub. As we build and deploy only from the main repo it may reduce frustration produced by the constant errors sent to the regular contributors. This fix switches from error notifications to "job skipped" notifications.