Make CI work on forks #2559
Labels
Milestone
Comments
|
This might be a new feature, but I think GitHub Actions supports running builds in forks with secrets, requiring approval before doing so (to avoid people trying to steal secrets using echo $ENV_VAR or whatever): https://docs.github.com/en/actions/reference/environments#environment-secrets |
jawnsy
added a commit
that referenced
this issue
Mar 12, 2021
* Run builds when changes are pushed to the main branch, or for pull requests opened against the main branch. This is a subtle change in behavior because, previously, builds would've run on pushes to any branch, regardless if a pull request is open yet. * Update to GitHub actions/checkout v2, which performs a shallow clone by default, and should speed up the build. Closes: #2559
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unfortunately github actions CI will only work on forks if there are no custom secrets.
So the npm package and docker image release process will have to be ran manually instead of via CI. Those are also in a separate workflow and github actions still won't run the workflow that does not depend on any secrets.
It's a worthy tradeoff to make it easier for contributors to get feedback on their changes.
The text was updated successfully, but these errors were encountered: