add 1 sentence humanized descriptions to the ward comments go code #1260

Merged
coilyco-ops merged 2 commits from issue-1201 into main 2026-07-14 09:51:13 +00:00
Member

This adds humanized inline comments to the canonical wardedWorkflowCommentVariants array in cmd/ward/workflow_comment.go, so each workflow status reads like a sentence instead of a bare enum label.

The parser and emitted headers stay unchanged. This is a documentation-only code comment update for the workflow comment constants.

  • What changed: one-sentence descriptions on each central workflow variant.
  • Why: the array should explain itself to readers without changing behavior.
  • Tests: pre-commit run --all-files and ward exec test passed locally.

closes #1201
ward.workflow: pull-request-and-merge

This adds humanized inline comments to the canonical `wardedWorkflowCommentVariants` array in `cmd/ward/workflow_comment.go`, so each workflow status reads like a sentence instead of a bare enum label. The parser and emitted headers stay unchanged. This is a documentation-only code comment update for the workflow comment constants. - What changed: one-sentence descriptions on each central workflow variant. - Why: the array should explain itself to readers without changing behavior. - Tests: `pre-commit run --all-files` and `ward exec test` passed locally. closes #1201 ward.workflow: pull-request-and-merge
docs: add workflow comment helper summaries
All checks were successful
test / test (pull_request) Successful in 45s
48d4e7c47c
docs: humanize workflow variants
All checks were successful
test / test (pull_request) Successful in 1m21s
c7fe5a962a
Author
Member

WARDED_WORKFLOW: blocked 🛑

details

workflow: pull-request-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default
felt: the implementation itself was straightforward, but Forgejo Actions stayed stuck in waiting, so the merge path is blocked on the platform, not the diff.
confidence: medium
surprises: run #2002 never left waiting after repeated polls.
follow-ups: wait for the runner queue to clear, then rerun the workflow and finish the merge.

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default felt: the implementation itself was straightforward, but Forgejo Actions stayed stuck in waiting, so the merge path is blocked on the platform, not the diff. confidence: medium surprises: run #2002 never left waiting after repeated polls. follow-ups: wait for the runner queue to clear, then rerun the workflow and finish the merge. </details>
Sign in to join this conversation.
No description provided.