mirror of
https://github.com/bevyengine/bevy
synced 2024-12-19 01:23:09 +00:00
24c3bd5f00
# Objective The weekly beta compile test workflow can be useful to people who have forked the repository. However, there are a few small issues with how this workflow is currently set up: * Scheduled workflows run on the base/default branch, with no way (currently) to change this. On forks, the base/default branch is usually kept in sync with the main Bevy repository, meaning that running this workflow on forks would just be a waste of resources. (See [here](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#schedule) - "Scheduled workflows will only run on the default branch.") * Even if there was a way to change the branch that a scheduled workflow runs on, forks default to not having an issue tracker. * Even in the event that a fork's issue tracker is enabled, most users probably don't want to receive automated issues in the event of a compilation failure. Because of these reasons, this workflow is irrelevant for 99% of forks. ## Solution We now skip all jobs on the `Weekly beta compile test` workflow, if we detect we're running this workflow on a fork. ## Testing Testing? Who needs testing? (Seriously though, I made sure the syntax is correct.) |
||
|---|---|---|
| .. | ||
| action-on-PR-labeled.yml | ||
| ci-comment-failures.yml | ||
| ci.yml | ||
| daily.yml | ||
| dependencies.yml | ||
| docs.yml | ||
| post-release.yml | ||
| release.yml | ||
| send-screenshots-to-pixeleagle.yml | ||
| validation-jobs.yml | ||
| weekly.yml | ||
| welcome.yml | ||