docs: fix 329 Microsoft.Contractions hits with proper safety checks
Apply contraction fixes across ~40 doc files (setup, integrations, lifecycle, networking, scheduler, swarm, tools, trust-boundary, UI, etc.). Skipped 14 hits: - 10 where words appear in ALL CAPS for deliberate emphasis (is NOT, do NOT, etc.) - 4 where text could not be safely located due to markdown formatting or column position Applied via systematic scan with checks for fenced code blocks, inline code spans, and intentional caps. Preserves sentence-initial capitalization throughout.
This commit is contained in:
parent
77296aff35
commit
78021ce982
38 changed files with 320 additions and 320 deletions
|
|
@ -32,7 +32,7 @@ list (show/create/edit/status/merge/reviews/commits/diff/view/comment/
|
|||
comments/close/reopen/labels/assign/dependency/reaction/timeline as applicable).
|
||||
|
||||
The flat forms are two different groups, and `--help` hides both, so the
|
||||
difference cannot be seen from the CLI and is stated here instead:
|
||||
difference can't be seen from the CLI and is stated here instead:
|
||||
|
||||
- **Renamed — these no longer run.** `issue-create` `issue-edit` `pr-create`
|
||||
`pr-status` `pr-merge` `pr-reviews` `pr-commits` `pr-assign-reviewer` `diff`
|
||||
|
|
@ -40,7 +40,7 @@ difference cannot be seen from the CLI and is stated here instead:
|
|||
are removed outright in a later release.
|
||||
- **Kind-agnostic — these stay.** `view` `comment` `comments` `close` `assign`
|
||||
`labels` `timeline` are the only way to act on a number without already
|
||||
knowing whether it is an issue or a PR, which no namespaced form offers.
|
||||
knowing whether it's an issue or a PR, which no namespaced form offers.
|
||||
Hidden, but supported; prefer `issue <verb>` / `pr <verb>` when the kind is
|
||||
known, since those validate it.
|
||||
|
||||
|
|
@ -217,7 +217,7 @@ plain comment show under `last comment`, not `reviews`.
|
|||
|
||||
### Repo management
|
||||
|
||||
Agents **cannot create repos directly via forge token** — Forgejo
|
||||
Agents **can't create repos directly via forge token** — Forgejo
|
||||
disables push-to-create and the agent token doesn't have the Create
|
||||
scope. Two paths exist depending on where the repo should live:
|
||||
|
||||
|
|
@ -225,7 +225,7 @@ scope. Two paths exist depending on where the repo should live:
|
|||
MCP tool (requires the `forge` tool group). hive-c0re creates the repo in
|
||||
the c0re-owned `agents/` org, adds you as a write collaborator (not
|
||||
owner), and enables branch protection (operator-team merge approval
|
||||
required — you cannot self-merge). Clone URL is returned immediately.
|
||||
required — you can't self-merge). Clone URL is returned immediately.
|
||||
This is the standard path for agents that need a working repo.
|
||||
|
||||
**Other repos** — Use the CLI verbs below (`repo-create` / `repo-add-collaborator`).
|
||||
|
|
@ -346,7 +346,7 @@ to discover valid label names before triaging or to audit the label set.
|
|||
normal query).
|
||||
- ⚠️ `--assignee` / `--author` are deliberately **not** validated: someone
|
||||
who has left still legitimately appears on old issues, so a login that
|
||||
isn't a current member is not necessarily a typo.
|
||||
isn't a current member isn't necessarily a typo.
|
||||
- `list --limit N` is a *request*: the forge clamps page size to its own
|
||||
`api.MAX_RESPONSE_ITEMS` (50 by default), so `--limit 400` returns at
|
||||
most 50 rows. The stderr trailer reports the real total from the
|
||||
|
|
|
|||
Loading…
Reference in a new issue