#293: tag rancher release #315
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tashima42
force-pushed
the
293-tag-rancher-release
branch
from
a7789a3 to
9a6aaba
Compare
|
Is there any requirement to run this from a specific directory/repo path? |
|
No |
briandowns
approved these changes
Nov 29, 2023
brooksn
approved these changes
Nov 30, 2023
tashima42
added a commit
to tashima42/ecm-distro-tools
that referenced
this pull request
Dec 19, 2023
* add rancher tag release command * add release body generation with rancher/rancher * add documentation * fix import * fix pull * move types to top * add tests * remove components file * remove unued struct run component files args --------- Co-authored-by: Pedro Tashima <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #293
Adds a command to tag rancher releases
How to test
Refer to examples in the documentation.
Please make sure to either run it with
--dry-runor in a fork.