Use central github-actions repo for jira-release-sync#217
Merged
Conversation
Point the Jira release sync workflow at the v1 tag of the ThePalaceProject/github-actions repository instead of the inline action in the circulation repo.
jonathangreen
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Update the Jira release sync workflow to use the centralized
jira-release-syncaction from the newThePalaceProject/github-actionsrepository, pinned to thev1tag, instead of the inline action underThePalaceProject/circulation/.github/actions/jira-release-sync@main. Also drops theactions/checkoutstep since the action does not require the repository to be checked out.Motivation and Context
The
jira-release-syncaction has been moved to a centralgithub-actionsrepository so it can be shared and versioned across Palace repos. This switches us over to the new location and pins tov1.How Has This Been Tested?
No code changes — only workflow updates. Will be exercised the next time a release is published.
Checklist: