Document that merging to main doesn't publish to ClawHub or npm - #10
Closed
michaelmagan wants to merge 1 commit into
Closed
Document that merging to main doesn't publish to ClawHub or npm#10michaelmagan wants to merge 1 commit into
michaelmagan wants to merge 1 commit into
Conversation
Just watched a skills/** change (the product-context line, then the app-building-guide rewrite) merge to main and sit unpublished on ClawHub for a day, because clawhub-publish.yml only really syncs on a release event — a PR merge only runs its dry-run branch. Nothing on main said so anywhere a contributor would see it before hitting it. Add a "Releasing" section to CONTRIBUTING.md spelling out the tag-push flow (npm + GitHub release + ClawHub sync in one shot), and flag the gap directly in the workflow's own header comment. Co-Authored-By: Claude Sonnet 5 <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.
Summary
maindoesn't publish anything.clawhub-publish.ymlonly runs a--dry-runon a PR; the realsync(withCLAWHUB_TOKEN) fires onrelease: publishedonly, and nothing onmaintriggers a release by itself. Two skill changes (Add product context and install line to the skill body #8, Turn the charming skill into an app-building guide, not just a CLI reference #9) sat merged and unpublished until this was caught.CONTRIBUTING.mdspelling out the actual flow: bumppackage.json, merge, thengit tag vX.Y.Z && git push origin vX.Y.Z— that tag push runsbun run check, publishes npm, creates the GitHub release, and (via that release event) syncs ClawHub, all in one shot. Also notes the manualworkflow_dispatchescape hatch for a ClawHub-only sync.clawhub-publish.yml's header comment, pointing back at CONTRIBUTING.md.No workflow behavior changed — comments and docs only.
🤖 Generated with Claude Code