Skip to content

Conversation

@dustinblack
Copy link
Member

Changes introduced with this PR

add release building to carpenter config


By contributing to this repository, I agree to the contribution guidelines.

Copy link
Contributor

@jaredoconnell jaredoconnell left a 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.

Copy link
Contributor

@jaredoconnell jaredoconnell left a 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.

@dustinblack dustinblack merged commit 6c9e088 into main Jan 3, 2023
@dustinblack dustinblack deleted the carpenter-release branch January 3, 2023 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants