Nathan Stocks dd7f800b25 Only run some workflows on the bevy repo (not forks) (#9872) ... # Objective Eliminate unnecessary Actions CI builds on forks, such as: - Daily builds, which are a waste of compute on forks, even if they succeed (although the Android build fails) - Administrative builds that attempt to deploy something In both the cases above, forks get CI failures that need to be ignored. It looks like this: <img width="1178" alt="image" src="https://github.com/bevyengine/bevy/assets/5838512/6365059a-1170-4bba-9c60-3e252ae7779f"> <img width="1186" alt="image" src="https://github.com/bevyengine/bevy/assets/5838512/ab824a0b-5202-42f7-a24f-95c5cd53376c"> ## Solution - [Only run some jobs when they are in the `bevyengine/bevy` repo.](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-only-run-job-for-specific-repository) - Leave the rest of the workflows alone (you still get a full set of CI for pull requests, for example) ---		2023-09-20 18:22:34 +00:00
..
action-on-PR-labeled.yml	add an action to ask for a migration guide when one is missing (#7507)	2023-02-05 14:21:44 +00:00
ci-comment-failures.yml	switch CI jobs between windows and linux for example execution (#9489)	2023-08-19 14:47:41 +00:00
ci.yml	Bump actions/checkout from 2 to 4 (#9759)	2023-09-13 19:26:25 +00:00
daily.yml	Only run some workflows on the bevy repo (not forks) (#9872)	2023-09-20 18:22:34 +00:00
dependencies.yml	Bump actions/checkout from 2 to 4 (#9759)	2023-09-13 19:26:25 +00:00
docs.yml	Only run some workflows on the bevy repo (not forks) (#9872)	2023-09-20 18:22:34 +00:00
post-release.yml	Only run some workflows on the bevy repo (not forks) (#9872)	2023-09-20 18:22:34 +00:00
release.yml	Only run some workflows on the bevy repo (not forks) (#9872)	2023-09-20 18:22:34 +00:00
validation-jobs.yml	Bump actions/checkout from 2 to 4 (#9759)	2023-09-13 19:26:25 +00:00
welcome.yml	Fix CI welcome message (#7428)	2023-01-30 20:21:06 +00:00