Skip to content

Require passive voice and Gardener attribution in dispatched GitHub content - #83

Merged
dmccoystephenson merged 1 commit into
mainfrom
feature/attribution-passive-voice
Aug 3, 2026
Merged

Require passive voice and Gardener attribution in dispatched GitHub content#83
dmccoystephenson merged 1 commit into
mainfrom
feature/attribution-passive-voice

Conversation

@dmccoystephenson

Copy link
Copy Markdown
Member

Summary

  • Any GitHub content a dispatched run writes on the operator's behalf (PR descriptions, issue bodies, PR/issue comments) is written under the operator's own gh identity, so it's otherwise indistinguishable from something they wrote by hand.
  • Adds dev_loop.ATTRIBUTION_REQUIREMENT (+ GARDENER_REPO_URL): every such piece of content must be in passive voice and include a disclosure line noting it was drafted during a Gardener session, linking this repo. Commit messages stay exempt — those already follow COMMIT_PR_CONVENTIONS.md's own style.
  • Wired into the three places gardener currently writes GitHub content: align --implement, align --file-issue (cli.py's MODE_INSTRUCTIONS), and tend (dev_loop.py's build_tend_prompt).

Test plan

  • PYTHONPATH=. python3.11 -m unittest discover -s tests — 553 tests, all pass
  • New tests assert the requirement text and repo URL appear in the align --implement, align --file-issue, and tend prompts

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

…ontent

A PR/issue a dispatched run opens is written under the operator's own gh
identity, so it's otherwise indistinguishable from one they wrote by hand.
Every place gardener writes GitHub content on their behalf (align
--implement/--file-issue, tend) now must use passive voice and disclose
that it was drafted during a Gardener session, linking the repo.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@dmccoystephenson
dmccoystephenson merged commit c33f01a into main Aug 3, 2026
2 checks passed
@dmccoystephenson
dmccoystephenson deleted the feature/attribution-passive-voice branch August 3, 2026 05:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant