fix: change action name to 'Setup Goose CLI' for marketplace uniqueness#6
Merged
fix: change action name to 'Setup Goose CLI' for marketplace uniqueness#6
Conversation
clouatre
added a commit
that referenced
this pull request
Nov 13, 2025
5 tasks
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.
Problem
GitHub Marketplace rejected the action name
Setup Goosewith error:Root cause:
mscno/setup-gooseexists (installs Pressly's database migration tool), causing a name collision even though they're completely different tools:Solution
Changed action name to
Setup Goose CLIRationale
Setup Sentry CLI,Setup Arduino CLIgithub.com/marketplace/actions/setup-goose-cliChanges
action.ymlline 1:name: 'Setup Goose'→name: 'Setup Goose CLI'Breaking Changes
None. Users reference actions by repository (
clouatre-labs/setup-goose-action@v1), not by action name. The action name only affects:Existing workflows will continue to work without modification.
Next Steps
After merge:
Type: Bug fix
Scope: Marketplace publication requirement
Risk: None (metadata-only change)