Repository navigation
ci: use shared setup-github-bot action - #110
Merged
Merged
Conversation
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
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.
🧑💻What is the change being made?
Replace the local
./.github/workflows/setup-github-botcomposite action with the sharedtechcode-io/github-actions/setup-github-bot@setup-github-bot/v1in thepre-releaseandreleaseworkflows, and delete the local copy.❓ Why is the change being made?
The same action now lives in the shared techcode-io/github-actions repository. Using it removes a duplicated copy from this repo so updates happen in one place.
✅ How has this been tested?
Compared the shared action's
action.ymlwith the local one: both run the samegit configsteps for thegithub-actions[bot]identity, so the release jobs should behave the same. The workflows have not been run yet; the next pre-release run will exercise the change.📚 How has this been documented?
No documentation change is needed: the action is internal to CI and not described in the project docs.