docs(gws-shared): add community guidance for stars + issue hygiene#41
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
🦋 Changeset detectedLatest commit: 8e53d34 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
jpoehnelt
left a comment
jpoehnelt
left a comment
There was a problem hiding this comment.
Thanks for PR #41! This is a great addition and prevents ongoing whack-a-mole patching.
The resolve_name fallback is much more robust than aliasing individual commands.
I just wrote up Issue #45 documenting this exact problem, but it appears Issue #32 already existed, and this PR addresses it elegantly by standardizing all resource and method subcommands to resolve properly from kebab-case.
The mut path: Vec<String> allocation is clean as it takes ownership from clap.
Also a good catch updating .any to .contains where there was a .clippy warning for clarity.
Looks good to me! LGTM.
jpoehnelt-bot
force-pushed
the
chore/gws-shared-community-guidance
branch
from
9a17e31 to
ed0ce11
Compare
…oogleworkspace#41) * docs(gws-shared): add community issue and starring guidance * feat: add community links to gws help output * fix(ci): move community section into generate-skills template + add changeset
2 participants
Summary
skills/gws-shared/SKILL.mdWhy
This adds explicit guidance to reduce duplicate issues and improve signal in issue tracking while encouraging lightweight project support.
File changed
skills/gws-shared/SKILL.md