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
{{ message }}
Repository navigation
A Pre-Existing Comment in the Documented Aggregator Stub Wraps Mid-Sentence #1232
docs/reusable-workflows.md's "Adopting the Gates" section, in the release-with-smoke stub's smoke-build job, carries a two-line comment that wraps one sentence across both lines:
# On a pull_request event github.ref_name is the PR ref (for example 123/merge), never the target branch,# so the logical branch reads base_ref first and only falls back to ref_name on a non-PR trigger.
.agents/skills/comment-and-doc-style/SKILL.md "Comments": "Structured, not prose: one sentence per line, never wrapped across lines, never a multi-sentence run-on. A comment that genuinely needs several sentences is several lines, each one sentence." This comment is one sentence split across two # lines, and its second line also opens lowercase ("so the logical..."), against the same section's "A comment line opening prose starts with a capital" rule.
Provenance
Confirmed present, unchanged, on develop at commit 6525cb8 (predates #1211's fix). Not introduced by #1211's PR (#1228); found by that PR's local-strict-review pass as an adjacent, out-of-scope defect in the same file.
Suggested resolution
Reflow into two complete sentences, one per line, e.g.:
# On a pull_request event github.ref_name is the PR ref (for example 123/merge), never the target branch.# The logical branch therefore reads base_ref first and only falls back to ref_name on a non-PR trigger.
Rolled up per #1315 into the unit tracker(s) #1360: every finding this issue enumerates appears there as a numbered line naming this issue. Closing as a duplicate of those trackers so no finding is lost and this bundle stops being a unit of work.
Activity
Match the Documented Aggregator Stub to the Hub's Own Workflow (#1228)
Promote Develop to Main: Settle Section 5 and the CRLF Chain (#1263)
ptr727 commentedon Sep 5, 2026
Rolled up per #1315 into the unit tracker(s) #1360: every finding this issue enumerates appears there as a numbered line naming this issue. Closing as a duplicate of those trackers so no finding is lost and this bundle stops being a unit of work.