-
Notifications
You must be signed in to change notification settings - Fork 8
add release building to carpenter config #22
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
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.
The reference to the github repo name is good. That lowers the chance of someone forgetting to update the template, resulting in the wrong image name.
The only downside is it requires the repository name to match, but that is definitely the best practice.
It's also good to do releases for tags.
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.
The newest version of this is much less redundant, which is great! And I see you dynamically specified the name to address the clarity problems you were concerned about, so that's good.
Looks good to me. Just make sure you fix the CI issue before merging.
Changes introduced with this PR
add release building to carpenter config
By contributing to this repository, I agree to the contribution guidelines.