Skip to content

Commit ac9b3e7

Browse files
committed
docs: update AGENTS.md and CLAUDE.md ๐Ÿ‘ฎ
1 parent 64bd5e7 commit ac9b3e7

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

โ€ŽAGENTS.mdโ€Ž

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,6 @@ Add language behavior tests as `.ndc` programs under `tests/programs/<category>/
2727
## Commit & Pull Request Guidelines
2828
Use Conventional Commit subjects for commits and pull request titles: `feat`, `fix`, `refactor`, `perf`, `style`, `test`, `docs`, `build`, `ops`, and `chore`. Scopes are optional. When a scope helps, prefer a crate or subsystem such as `lexer`, `parser`, `vm`, `compiler`, or `lsp`, for example `fix(parser): handle trailing commas`.
2929

30-
This repository uses squash merging for pull requests, so every PR title must conform to the Conventional Commit format because it becomes the final merged commit message. If you include an emoji in a commit or PR title, place it at the end of the title rather than the beginning, for example `perf(lexer): make token scanning faster ๐ŸŒ` or `refactor(lsp): move completion logic into handlers ๐Ÿงน`.
30+
This repository uses squash merging for pull requests, so every PR title must conform to the Conventional Commit format because it becomes the final merged commit message. You must include an emoji in a commit or PR title, place it at the end of the title rather than the beginning, for example `perf(lexer): make token scanning faster ๐ŸŒ` or `refactor(lsp): move completion logic into handlers ๐Ÿงน`.
3131

32-
PRs should describe the behavioral change, link the relevant issue or PR when applicable, and call out AI-generated contributions as requested in `README.md`. Include screenshots only for editor-extension UI changes.
32+
PRs should describe the behavioral change, link the relevant issue or PR when applicable, and call out AI-generated contributions as requested in `README.md`.

โ€ŽCLAUDE.mdโ€Ž

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Source โ†’ [Lexer] โ†’ Tokens โ†’ [Parser] โ†’ AST โ†’ [Analyser] โ†’ Annotated
6565
- Use Conventional Commit subjects for commits and pull request titles: `feat`, `fix`, `refactor`, `perf`, `style`, `test`, `docs`, `build`, `ops`, `chore`
6666
- Scopes are optional; when a scope helps, prefer a crate or subsystem such as `lexer`, `parser`, `vm`, `compiler`, or `lsp`
6767
- This repository uses squash merging, so every pull request title must already be a valid Conventional Commit subject because it becomes the merged commit message
68-
- If an emoji is included in a commit or pull request title, place it at the end of the title, for example `perf(lexer): make token scanning faster ๐ŸŒ`
68+
- Included an emoji in a commit or pull request title. Place it at the end of the title, for example `perf(lexer): make token scanning faster ๐ŸŒ`
6969
- Branch names use category prefixes: `feature/`, `bugfix/`, `housekeeping/`, etc.
7070

7171
### Crate Layout

0 commit comments

Comments
ย (0)