docs(register): reduce internal jargon in adopter-facing workflow YAML + script top-of-file comments #313
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#313
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Lookout Codeberg cold-read (bus 45db) flagged:
.forgejo/workflows/*.ymlandscripts/*.shcomments carry too much incident archaeology + internal jargon for public first-glance readers. Terms likesubstrate-honest,path-alpha,mechanism-of-touch,operator directiveshow up in files adopters will copy-paste. As a maintainer, useful; as a newcomer, confusing.Scope
reusable-release.yml,reusable-manifest-check.yml,reusable-changelog-*.yml) — top-of-file#documentation blocks + inline commentsscripts/release-decide.sh,scripts/release-prep.sh,scripts/draft-release.sh,scripts/manifest-check.sh)# See ADR-0007 for path-α rationale)Set J context
Must land before v1.0.0. QM substrate-familiar — knows which comments are load-bearing context vs archaeology-nostalgia.