Create a new workflow to create a release and tag in the repository #1377
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
jjkiely
force-pushed
the
add-tagRelease-workflow
branch
from
63cea00
to
024219a
Compare
|
@eguzki I see you're a member of APIcast core can you review this one as well when you get the chance please? |
eguzki
approved these changes
Oct 13, 2022
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.
Create a new github actions workflow to create releases and tags in the repo, this is part of ongoing work to migrate the upstream tagging job away from jenkins due to the decommissioning of the instance in the near future.
This action will be manually triggerable (to create a tag in this repo alone) but can also by triggered by another action which can create tags in all upstream repos at once, similar to the old jenkins job.