-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore: configure some actions to be skipped for forks #2005
Conversation
Sorry I completely missed this, can you rebase? |
0058a90
to
c11f8e2
Compare
I rebased it, but I'm not sure about the Docs deployment now. I see it's building it whenever you push to main, but I still feel that it is not really necessary for the forked repositories. |
You're right. Docs should probably only get built/pushed when either But building and pushing should still work in a fork; I use this to render previews of proposed doc changes. |
c11f8e2
to
d580d32
Compare
Okay, let's keep it then. I removed the if condition from the docs and added that we should only run the build on push if the paths relevant to the docs change. |
Looks good to me, I'll let @nblock has the final say about the docs pipeline |
This is just a simple change.
This will configure some actions to be skipped for forks, as the actions that are changed here depend on the main repository or the configured secrets, so it makes no sense to run them for forks. This will also remove failed cron jobs from the forks, rest of the actions that don't depend on anything are left untouched.