Skip to content

Make build/release script menus self-documenting - #54

Merged
lotech merged 1 commit into
mainfrom
claude/security-audit-9zh0F
May 23, 2026
Merged

lotech merged 1 commit into
mainfrom
claude/security-audit-9zh0F

Conversation

@lotech

@lotech lotech commented May 23, 2026

Copy link
Copy Markdown
Owner

Add purpose banners to the interactive menus of build.sh and release.sh so each explains what it does, how it differs from the other, and that flags are optional shortcuts (running with no arguments is the easy path).

Document the build-vs-release distinction and a common-tasks quick reference in RELEASING.md, and clarify in the README that build.sh is the local-dev helper while release.sh is the maintainer publish flow.

https://claude.ai/code/session_0187mF1SLDKYAwvRpob7xC6B

Summary

Brief description of the changes.

Changes

  • …

Checklist

  • Builds without warnings on macOS 13+
  • Tested with at least one HID device
  • No new SwiftLint violations
  • Updated CHANGELOG.md if user-facing

Add purpose banners to the interactive menus of build.sh and release.sh
so each explains what it does, how it differs from the other, and that
flags are optional shortcuts (running with no arguments is the easy path).

Document the build-vs-release distinction and a common-tasks quick
reference in RELEASING.md, and clarify in the README that build.sh is the
local-dev helper while release.sh is the maintainer publish flow.

https://claude.ai/code/session_0187mF1SLDKYAwvRpob7xC6B
@lotech
lotech merged commit b917fbc into main May 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants