bevy
bevy copied to clipboard
Add `cargo ci` alias for `ci` tool
Objective
- Running
cargo run --package ci -- ...is lengthy, andcargo r -p ci -- ...isn't much better. - Closes #13197.
Solution
- Add an opt-in alias to the
citool withcargo ci ....- You need to copy
config_fast_builds.tomltoconfig.tomlto enable this functionality.
- You need to copy
Testing
- Copy
config_fast_builds.tomltoconfig.toml, then runcargo ci --help.
Changelog
- Added
cargo cialias for internalcitool.
It's unfortunate that this is opt-in, but this is the least-friction solution. The alternative probably would involve:
- Renaming
config_fast_builds.tomltoconfig.toml, breaking a few links on the website. - Remove
config.tomlfrom.gitignore. - Disable all of the fast-build shenanigans by default.
The issue with that is that all changes to config.toml, such as enabling fast builds, would be tracked by Git. I feel like that would interfere with the development workflow too much that it does not justify the change.
Given #13279. Could we add a setup command to our CI tool that asks the contributor some questions and then setups the config.toml for them?
That sounds like a great follow-up PR! I'll create an issue for it.