mirror of
https://github.com/bevyengine/bevy
synced 2024-11-10 07:04:33 +00:00
2f87bb8c1f
# Objective - Some developers enable Github Actions for their fork and commit directly to main. This triggers the `docs.yml` action, which attempts to deploy the documentation even if Github Pages is not enabled. (It also creates a `CNAME` file specific to Bevy and should not be used in forks, even for testing.) - For an example, see [this run](https://github.com/tychedelia/bevy/actions/runs/8978912060/job/24660082729). ## Solution - Only attempt to deploy docs when running from the main Bevy repository. - This does not affect us checking `cargo doc` on pull requests, since that it done in `ci.yml`. ## Testing It's difficult to test this, but you'd probably: 1. Fork Bevy 2. Cherry pick this PR's commits onto the main branch of your fork. 3. Push another commit to the main branch, triggering Github Actions. 4. Check the Github Actions job summary to ensure that the `build-and-deploy` job is skipped. |
||
|---|---|---|
| .. | ||
| actions/install-linux-deps | ||
| contributing | ||
| example-run | ||
| ISSUE_TEMPLATE | ||
| linters | ||
| start-mobile-example | ||
| start-wasm-example | ||
| workflows | ||
| dependabot.yml | ||
| FUNDING.yml | ||
| pull_request_template.md | ||