-
Notifications
You must be signed in to change notification settings - Fork 13
Add a checkbox to retarget any related tags #63
Copy link
Copy link
Open
Labels
documentationThis issue or pull request improves or adds to documentationThis issue or pull request improves or adds to documentationgood first issueThis issue or pull request is well-defined and good for newcomersThis issue or pull request is well-defined and good for newcomershacktoberfest-acceptedPull request that should count toward Hacktoberfest participationPull request that should count toward Hacktoberfest participationimprovementThis issue or pull request will add or improve functionality, maintainability, or ease of useThis issue or pull request will add or improve functionality, maintainability, or ease of use
Metadata
Metadata
Assignees
Labels
documentationThis issue or pull request improves or adds to documentationThis issue or pull request improves or adds to documentationgood first issueThis issue or pull request is well-defined and good for newcomersThis issue or pull request is well-defined and good for newcomershacktoberfest-acceptedPull request that should count toward Hacktoberfest participationPull request that should count toward Hacktoberfest participationimprovementThis issue or pull request will add or improve functionality, maintainability, or ease of useThis issue or pull request will add or improve functionality, maintainability, or ease of use
Type
Fields
Give feedbackNo fields configured for issues without a type.
After a release is made we should retarget any tags that need it. For example. If the current repo is at
v1.0.0and there is av1tag that points to the same commit... when we make thev1.0.1release, thev1tag should be moved to point to the same commit.An example of this can be found in
cyhy-config:Which is referenced by
cyhy-kevsync:An example of
For extra credit, find or write a GitHub Action that can do this automatically upon the generation of a release.
.github/.github/pull_request_template.md
Line 60 in ad719df