Adopt Scoped Commits for this repo - #14
Merged
Merged
Conversation
Records the commit format in agents.md so it travels with the repo and is found by agents working from a fresh checkout. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TDfmMveB3PoZ46yuy8htr4
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
2 participants
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.
Adopts Scoped Commits as this repo's commit message format and writes the convention into
agents.md, so agents working from a fresh checkout find it without depending on anyone's personal config.Format is
<scope>: <description>, where the scope is the area of the tree the change touches and never a change type — sosettings: fix login redirectin place offix(settings): .... The rationale is that the type prefix is close to information-free (nearly every commit is a fix or a feat, and the description already says which), while the scope is the token that discriminates between log lines when scanning.Nothing breaks: no commit-message tooling exists in any FreeshardBase repo (no commitlint, semantic-release, conventional-changelog, release-please or changesets), versions are set explicitly, and GitHub's auto-generated release notes are built from merged pull requests rather than from commit subjects.
The scope list in this PR is a first pass, derived from the directory structure and the existing log. Adjust it in a follow-up if working in the tree shows it is at the wrong granularity.
Same change is going into the other active FreeshardBase repos.
🤖 Generated with Claude Code
https://claude.ai/code/session_01TDfmMveB3PoZ46yuy8htr4