3 Commits

Author	SHA1	Message	Date
MinerSebas	39271f24d2	Exclude some Branches from running CI (#2344) ... # Objective #2230 allowed the CI to run on every Branch of this Repo. But some Branches should not actually run the CI, which wastes the available capacity of CI runners. ### staging-squash-merge.tmp This Branch is used by Bors when squashing a PR. CI shouldn't need to run here, as the actual verification happens in the staging branch   ### dependabot/** Dependabot creates its branches in this Repo, which causes the CI to run twice on the same commit  ## Solution Exclude those branches from running CI.	2021-06-22 07:59:37 +00:00
François	bec323e2e2	remove branch constraints in CI (#2230) ... Remove branch constraints from CI This will let CI run on: - fork branches before a PR is opened - this repo branches if we start using them (😉 relations 😉 )	2021-05-23 19:51:34 +00:00
François	177f2fbf9a	enable cargo deny (#2101) ... https://github.com/EmbarkStudios/cargo-deny cargo-deny is a tool that can issue errors for dependency issues, among other: * security issues in a crate * duplicated dependencies with different versions * unauthorised license Added cargo-deny with an opinionated configuration: * No middle ground with warnings, either allow or deny * Not added to Bors, we probably don't want to block a PR on something that may happen from outside * Different github workflow than CI to run only when Cargo.toml files are changed, or on a schedule * Each check in its own job to help readability * Initial config makes Bevy pass all check Pushing a first commit with commented config to show errors	2021-05-17 23:07:18 +00:00