-
Notifications
You must be signed in to change notification settings - Fork 382
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
rthooks: image and helm fixes #2727
Conversation
While tagging rthooks/v0.1, the GH action that builds the images failed with: Error: buildx failed with: ERROR: failed to solve: target stage "release" could not be found Rename the final taret to release to fix this. Signed-off-by: Kornilios Kourtis <[email protected]>
Signed-off-by: Kornilios Kourtis <[email protected]>
The v0.1 tag failed to build, so let's move to the next. Signed-off-by: Kornilios Kourtis <[email protected]>
Signed-off-by: Kornilios Kourtis <[email protected]>
✅ Deploy Preview for tetragon ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
nit: The last 2 commits can be merged together in a single one. I believe that there will not be any case where reverting only one of those make sense. Feel free to ignore that for this PR, just a comment in general.
Thanks!
I agree wrt to reverting. I have the habit of splitting patches that change code with auto-generation to better deal with conflicts. I'll leave it as and merge the PR, but maybe it would make sense to come up with a general rule on whether we want to split auto-generation with everything else or not. I'm personally on the former camp, but it's just a preference. |
see patches.