-
Notifications
You must be signed in to change notification settings - Fork 2
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
justfile: Truncate tag names, everywhere necessary #66
Conversation
qmonnet
commented
Nov 9, 2024
- Revert "justfile: Truncate container tag string if too long"
- justfile: Truncate container tag string if too long (2nd attempt)
Not good yet |
e37c2b9
to
54311ab
Compare
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.
Maybe use truncate_str
as the function name?
54311ab
to
1246934
Compare
All tests passed this time! 🎉 |
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.
Yup. 💦 Spritzes holy water on commits 💦
This reverts commit 0874727. Turns out this commit missed a lot of occurrences where tag can be too long, let's find a more generic truncate function to solve the issue. Signed-off-by: Quentin Monnet <[email protected]>
Containers' tags can't be longer than 128 characters. Sometimes CI generates tags that are longer than this (thanks Dependabot for the extra-long branch names). Make sure we don't break docker builds by having bash truncate the string if necessary - everywhere we need it. Fixes: b88ec42 ("Build system") Signed-off-by: Quentin Monnet <[email protected]>
1246934
to
728171e
Compare
Side note, your preference is to always rebase on the current |
As long as we have
then I'm good. I love bisection methods and non-linear history and commits which don't build ruin it 🤷♀️ Really, we should open source this stuff and then we can just use the merge queue method |
We don't currently build each commit independently, do we? |
Not yet no. It is something I would like to get in place tho. I'm less stressed about it very early on in the project like this because it is unlikely we will care about bisection before we implement any real features. |