You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For quite some time now, I've been receiving notifications about failed pipelines. These notifications are being triggered because the jobs are currently running on forks as well.
While it's possible for me to simply disable all actions on the forked repository by navigating to Settings > Actions > Actions permissions and choosing "Disable Actions for this repository," I believe this solution is not ideal, as it would require every user who contribute to this project to perform this manual step individually.
Fortunately, GitHub provides a solution template to address this issue. The problem could be easily resolved by implementing an if condition, as demonstrated in the example provided in GitHub's documentation on workflow syntax for GitHub Actions: GitHub Actions Workflow Syntax Example
It might be worth considering this approach before making this repo the new main awesome-selfhosted repo.
The text was updated successfully, but these errors were encountered:
Strange, I do not get the same behavior when I fork the repo to my personal account. For me all workflows seem to be disabled by default, clicking on the Actions tab asks me to enable them manually:
For quite some time now, I've been receiving notifications about failed pipelines. These notifications are being triggered because the jobs are currently running on forks as well.
While it's possible for me to simply disable all actions on the forked repository by navigating to Settings > Actions > Actions permissions and choosing "Disable Actions for this repository," I believe this solution is not ideal, as it would require every user who contribute to this project to perform this manual step individually.
Fortunately, GitHub provides a solution template to address this issue. The problem could be easily resolved by implementing an if condition, as demonstrated in the example provided in GitHub's documentation on workflow syntax for GitHub Actions:
GitHub Actions Workflow Syntax Example
It might be worth considering this approach before making this repo the new main awesome-selfhosted repo.
The text was updated successfully, but these errors were encountered: