You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CLAUDE.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ return app.Execute(args);
96
96
- Nullable reference types enabled
97
97
- Warnings treated as errors
98
98
- Code style enforced in build (`EnforceCodeStyleInBuild=true`)
99
-
-Format check: `dotnet tool run dotnet-format`
99
+
-Run `dotnet format` to auto-fix formatting before committing
100
100
101
101
## Testing
102
102
@@ -130,6 +130,17 @@ The build script runs the complete validation pipeline including tests, samples,
130
130
131
131
This approach ensures code correctness, prevents regressions, and validates that tests actually catch the issues they're meant to detect. The test suite already has good coverage and patterns to follow.
132
132
133
+
## Pull Requests
134
+
135
+
When asked to fix an issue or implement a change via GitHub, follow this workflow:
136
+
137
+
1. Create a branch with the `claude/` prefix (e.g., `claude/fix-null-ref`, `claude/issue-123`). Never push directly to `main`.
138
+
2. Make the changes, following the TDD approach described above when applicable.
139
+
3. Run `pwsh -File build.ps1` to validate the full build passes before pushing.
140
+
4. Push the branch and open a PR.
141
+
5. Link the PR to the relevant issue using `Fixes #N` in the PR body.
142
+
6. Keep PRs focused — only change what's needed to address the issue. Don't refactor surrounding code or add unrelated improvements.
143
+
133
144
## Commit Guidelines
134
145
135
146
**IMPORTANT:** Use Conventional Commit format for all commit messages. This ensures consistency and enables automated changelog generation.
0 commit comments