-
Notifications
You must be signed in to change notification settings - Fork 15
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 mix deps.unlock --check-unused to CI #872
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to run a non cached execution? I think this execution should fail (it does in my local machine)
@arbulu89 yeah you're right, because we had a cache hit. Let's see if removing unused dependencies triggers the step |
@arbulu89 yeah looks like now the step was correctly executed, thanks for the heads up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool!
@@ -56,6 +56,7 @@ jobs: | |||
mix local.rebar --force | |||
mix local.hex --force | |||
mix deps.get | |||
mix deps.unlock --check-unused |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am late to the party, but this should be a listing step of "Static code analysis"
Description
As the team agreed upon during the planning, we are adopting
mix deps.unlock --check-unused
in our CI.Fixes # (issue)
Did you add the right label?
Aye
How was this tested?
If the CI is happy, we are I guess