-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest commits are not signed, breaking downstream CI #1307
Comments
@pinkforest FYI, everything needs to go through a PR workflow I went ahead and enabled "include administrators" in the branch protections |
Also the requirement for the commit to be signed is useless; I've filed rustsec/rustsec#629 to remove it. |
Yeah this was my stuff up 🤷♀️ my apologies - I don't typically like working in branch-in-origin-repo - I had cloned the .git from https:// instead of git@ and was working in the rustdecimal branch and had to switch to the git@ and then forgot to change the branch again. As to salt to the wounds that branch would require rebase so I went with another PR |
The last commit db78ca0 seems to break some CI integrations, because it's not a verified committer.
cargo-deny
fails to fetch the advisory database, with error:See e.g. this CI run.
The text was updated successfully, but these errors were encountered: