Whether a cargo-deny check succeeds or fails, doesn't entirely depend on the contents of a commit. e.g. new advisory could be released and make previously passing commits fail.
Therefore, it's a better idea to schedule the advisory checks based on a schedule, instead of per-commit, and open issues to notify the developer when checks fail.
Whether a cargo-deny check succeeds or fails, doesn't entirely depend on the contents of a commit. e.g. new advisory could be released and make previously passing commits fail.
Therefore, it's a better idea to schedule the advisory checks based on a schedule, instead of per-commit, and open issues to notify the developer when checks fail.