mirror of
https://github.com/bevyengine/bevy
synced 2024-12-24 12:03:14 +00:00
ec39f6b904
# Objective Running Github Actions on forks helps users to reduce the amount of CI errors they get before submitting a PR. However, due to how workflows are set up on the Bevy repository, this can result in errors occurring for jobs that may not be related to their PR - in this case, uploading screenshots to Pixel Eagle. ## Solution The Pixel Eagle workflow is skipped if we aren't running on the Bevy repository. If we are on the Bevy repository, or the user has set it to run elsewhere, we check if the `PIXELEAGLE_TOKEN` secret is set. If it isn't, we skip uploading screenshots to Pixel Eagle. * Artifacts still continue to generate, in case the user needs them. * In the event that the Pixel Eagle workflow runs, but the `PIXELEAGLE_TOKEN` secret isn't set, we generate a step summary that notifies the user of why it was skipped. https://github.com/LikeLakers2/bevy/actions/runs/12173329006/attempts/1#summary-33953502068 for an example. ## Testing Lots. And lots. Of trying to get Github Actions to work with me. |
||
|---|---|---|
| .. | ||
| 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 | ||