cargo/.github
bors 5e76f3491a Auto merge of #11761 - epage:deny, r=weihanglo
chore(ci): Enforce cargo-deny in CI

With #11448, we are pulling in a wide and deep dependency tree which makes it harder for us to track what we are pulling in over time.

I've been trying out [`cargo-deny`](https://github.com/EmbarkStudios/cargo-deny) on my projects and wanted to explore how useful it might be for cargo.  atm I only have it configured to fail for unexpected licenses.  We can also use its warnings to hunt down and remove duplicated dependencies to speed up our builds.

I did also enable advisories.  We ignore the failure in a way to not block PRs or even show up as failure in PRs as PR authors are not responsible for dealing with these (unless its a new dep) and it can be intimidating as a contributor to see a failure and have no idea how to resolve it (as authors generally assume CI is green and failures are there fault)

I did not go too much further into what all `cargo-deny` can do; there might be more we can leverage.
2023-03-02 21:40:09 +00:00
..
ISSUE_TEMPLATE Mention forum and zulip in feature-request issue template 2021-12-16 18:53:06 +08:00
workflows Auto merge of #11761 - epage:deny, r=weihanglo 2023-03-02 21:40:09 +00:00
PULL_REQUEST_TEMPLATE.md Add a notice about review capacity. 2022-03-24 14:18:42 -07:00