Use gdam-actions for install and publish - #1
Merged
Merged
Conversation
Both steps were copied by hand into fourteen repositories and had drifted into three variants each. They now come from the shared action, so a fix lands in one place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The
Install GDAMandPublish to GDAMsteps were copied by hand into 14 repos and had drifted into 3 variants each. They now come fromaviorstudio/gdam-actions@v0, so a fix lands in one place.The publish action derives the addon spec (
@aviorstudio/<repo>) and asset name (@aviorstudio_<repo>.zip) fromGITHUB_REPOSITORY— the same values this workflow passed explicitly.🤖 Generated with Claude Code