-
Notifications
You must be signed in to change notification settings - Fork 136
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
add lockfiles.yaml
+ rm and gitignore some unnecessary lockfiles
#1102
Conversation
Bencher
🚨 1 ALERT: Threshold Boundary Limit exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 7 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
Bencher
🚨 3 ALERTS: Threshold Boundary Limits exceeded!
Click to view all benchmark results
Bencher - Continuous Benchmarking View Public Perf Page Docs | Repo | Chat | Help |
e0279d3
to
bf27924
Compare
bf27924
to
89d91d3
Compare
89d91d3
to
33faa5d
Compare
33faa5d
to
04eb4e1
Compare
04eb4e1
to
8acc3fa
Compare
#1044 was closed, even though it was deleting those were still desirable changes, as stated on this comment #1044 (comment) so I'm also including those changes to this PR @jbesraa please let me know your thoughts here |
lockfiles.yaml
lockfiles.yaml
+ rm and gitignore some unnecessary lockfiles
I am a bit confused tbh. I think it was mentioned that we are not publishing the binaries anymore right? users just git clone and cargo install & run which I think anyway ignores cargo.lock file(unless you provide |
having lock files for binary crates is good practice this is another reason to keep roles and protocols in different workspaces |
@plebhash I dont wanna block this. Feel free to CP or add your own commits to ignore the libraries |
8acc3fa
to
15eb93c
Compare
15eb93c
to
5e282a4
Compare
The crates on
roles
andutils
generate binaries, which means it's a good engineering practice to keep{roles, utils}/Cargo.lock
on our git history.The root cause of the issues described on #1044 comes from the fact that we often bump dependency versions on
Cargo.toml
files without committing the same updates to the respectiveCargo.lock
.This PR introduces a new CI action that blocks PRs that change dependencies on the binary workspaces from being merged if they don't update
Cargo.lock
files accordingly.We also remove and gitignore
{protocols,benches/Cargo.lock}
since there's no need to keep them in the repository