KofTwentyTwo/standards
2
0 Fork 0
Code Issues 3 Pull Requests 3 Actions Packages Projects Releases 6 Wiki Activity

Use professional repository and release automation text #21

New Issue
Closed
opened 2026-10-10 17:47:17 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-10 17:47:17 +00:00 (Migrated from github.com)
Copy link
Copy source

The maintainer requires professional repository text with no emojis, joke copy, or bot sound effects. The current Release Please proposal contains its upstream default informal header and a decorative breaking-change heading, contrary to the existing personal preference.

Remove these defaults from future proposals, clean the current proposal, clarify professional-language guidance, and replace the remaining decorative IDE icon with its textual menu name. Use supported native release tooling and preserve semantic version calculations, breaking-change visibility, integrity checks, and immutable history.

Generated GitHub release notes may contain second-level category headings; ensure bundle notes include those sections and still stop at the next version heading. Keep already published artifacts and signed Git history unchanged.

The maintainer requires professional repository text with no emojis, joke copy, or bot sound effects. The current Release Please proposal contains its upstream default informal header and a decorative breaking-change heading, contrary to the existing personal preference. Remove these defaults from future proposals, clean the current proposal, clarify professional-language guidance, and replace the remaining decorative IDE icon with its textual menu name. Use supported native release tooling and preserve semantic version calculations, breaking-change visibility, integrity checks, and immutable history. Generated GitHub release notes may contain second-level category headings; ensure bundle notes include those sections and still stop at the next version heading. Keep already published artifacts and signed Git history unchanged.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
accessibility
Barrier affecting people with disabilities
 autorelease: failed
Reserved version tag; no published release
 autorelease: pending
autorelease: tagged
breaking
Incompatible new mandatory standards; requires a MAJOR release
 bug
Something isn't working
 dependencies
Pull requests that update a dependency file
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 release: failed
Reserved release tag failed before public publication; preserved for audit.
 release: ready
Maintainer-approved release preflight
 wontfix
This will not be worked on
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/standards#21