Skip to main content
← Back to list
01Issue
BugShippedSwamp Club
Assigneesstack72

Relationships

#701 Tutorial 'Publish an extension': examples hardcode @stack72 collective, breaks copy-paste publish step

Opened by sntxrrgithub · 6/19/2026· Shipped 6/19/2026

Affected page: https://swamp-club.com/manual/tutorials/publish-an-extension

The tutorial's example commands consistently use the literal collective name @stack72 (e.g. in swamp extension push @stack72/... and similar steps). Readers following the tutorial naturally copy-paste these examples verbatim.

When they reach the final publish step, the literal @stack72 collective doesn't belong to them, and the command fails:

18:45:42.403   fatal   error                Error: 'Extension collective "[@stack72](/u/stack72)" is not one of your collectives (@sntxrrgithub). Use one of: @sntxrrgithub'

Expected: the tutorial should use a generic placeholder (e.g. @your-collective) instead of a specific hardcoded collective, and should explicitly instruct readers to substitute their own collective before running the publish command.

Fix approach: replace the literal @stack72 references throughout the tutorial markdown with a placeholder token, and add a short callout reminding readers to swap in their own collective (visible via swamp whoami or equivalent) prior to the publish step.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

6/19/2026, 8:41:33 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack726/19/2026, 7:41:13 PM
Editable. Press Enter to edit.

stack72 commented 6/19/2026, 8:41:56 PM

Thanks @sntxrrgithub for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.