Use 'force-push semantics' (plural) in docs and code comments

Copilot · pelikhan · web-flow · commit 71a62a4ff341 · 2026-04-29T16:57:37.000Z
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/73c62235-cc79-479b-b145-e8529c7c8ee0 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
diff --git a/actions/setup/js/create_pull_request.cjs b/actions/setup/js/create_pull_request.cjs
@@ -466,7 +466,7 @@ async function handleRemoteBranchCollision(branchName, preserveBranchName, optio
 
   if (preserveBranchName) {
     // Reuse the existing branch by deleting the remote ref so the subsequent
-    // push recreates it from the local HEAD (force-push semantic). This is the
+    // push recreates it from the local HEAD (force-push semantics). This is the
     // intended behavior of preserve-branch-name for long-lived reusable
     // branches whose previous PR was merged.
     const { githubClient, owner, repo } = options;
diff --git a/docs/src/content/docs/reference/safe-outputs-pull-requests.md b/docs/src/content/docs/reference/safe-outputs-pull-requests.md
@@ -84,7 +84,7 @@ The `excluded-files` field accepts a list of glob patterns. Each matching file i
 
 The `preserve-branch-name` field, when set to `true`, omits the random hex salt suffix that is normally appended to the agent-specified branch name. This is useful when the target repository enforces branch naming conventions such as Jira keys in uppercase (e.g., `bugfix/BR-329-red` instead of `bugfix/br-329-red-cde2a954`). Invalid characters are always replaced for security, and casing is always preserved regardless of this setting. Defaults to `false`.
 
-When `preserve-branch-name: true` and the agent-supplied branch name already exists on the remote, the workflow reuses the existing branch by force-deleting the stale remote ref and recreating it from the agent's local HEAD (force-push semantic). This is the intended behavior for long-lived reusable branches whose previous PR was merged. The handler does not silently rename the branch in this case.
+When `preserve-branch-name: true` and the agent-supplied branch name already exists on the remote, the workflow reuses the existing branch by force-deleting the stale remote ref and recreating it from the agent's local HEAD (force-push semantics). This is the intended behavior for long-lived reusable branches whose previous PR was merged. The handler does not silently rename the branch in this case.
 
 The `draft` field is a **configuration policy**, not a default. Whatever value is set in the workflow frontmatter is always used &mdash; the agent cannot override it at runtime.
 
