-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix deployment --allow-dirty issue #177
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.
I would suggest you add a --allow-dirty flag instead
https://github.com/primait/umami/pull/1074
.cargo specifies a bunch of cargo, and it's a directory you want to commit to git
Why do you think you want to commit a directory of cached things? I think that Am i missing something? |
I thought allow-dirty would commit the clean state of the repo, but I was wrong, my bad.
it is not, that's only a thing in the prima specific rust CI, because we set CARGO_HOME there. Normally .cargo contains the cargo config(https://doc.rust-lang.org/cargo/reference/config.html) |
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'm not gonna block this on figuring out the perfect solution, since this will be fixed once we migrate to GHA, but can we just add a comment?
Co-authored-by: MaeIsBad <26093674+MaeIsBad@users.noreply.github.com>
I saw this issue: rust-lang/cargo#9398 |
The [build])https://drone-1.prima.it/primait/event_sourcing.rs/451/1/4) that failed because of dirty directory. The issue is that
.cargo
directory should be ignored