Skip to content

docs: require conventional commit format for PR titles #10310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ReubenBond merged 2 commits into from
Jul 31, 2026
Merged

docs: require conventional commit format for PR titles #10310

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c866dca
docs: require conventional PR titles
ReubenBond Jul 31, 2026
1f8c5a1
Potential fix for pull request finding
ReubenBond Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@
- Push feature branches to your personal fork, which is configured as `origin`.
- Create PRs using `dotnet/orleans` as the base repository and `origin`/personal fork branches as the head.
- Use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for commit messages from now on.
- PR titles must also follow Conventional Commits naming conventions because squash merges use the PR title as the resulting commit message.
- When creating PRs, keep the PR description simple: explain the problem it addresses and the solution it implements, including the rationale where helpful. Do not include a section describing what commands to run to test the PR.

Example:
Expand Down
Loading