From c866dcae0f3ce84d228f5dd175a5506f71cb65eb Mon Sep 17 00:00:00 2001 From: Reuben Bond Date: Fri, 31 Jul 2026 11:10:09 -0700 Subject: [PATCH 1/2] docs: require conventional PR titles Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: d9616733-f549-49b0-9a36-21810c299420 --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index a60eadeb8ed..2aa4a39a28d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -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-and-rebase 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: From 1f8c5a142ffda54ede1b86c582c080a893386f2d Mon Sep 17 00:00:00 2001 From: Reuben Bond <203839+ReubenBond@users.noreply.github.com> Date: Fri, 31 Jul 2026 11:14:55 -0700 Subject: [PATCH 2/2] Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 2aa4a39a28d..4651cd43fba 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -6,7 +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-and-rebase merges use the PR title as the resulting commit message. +- 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: