Repository navigation
fix(running-in-ci): prohibit self-authored attribution sign-offs - #773
Merged
Merged
Conversation
The bot occasionally appended a self-authored sign-off to PR bodies (e.g. "> _This was written by Claude Code on behalf of @max-sixty_"), re-introducing the Claude attribution that #759/#760 removed from the harness footer. No template emits this — it is emergent model self-attribution — so it needs an explicit prohibition the model reads each run. Extend the existing footer prohibition in the Comment Formatting section, which already governs the analogous case, to also cover authorship sign-offs on PR and issue bodies. Closes #772
max-sixty
added a commit
that referenced
this pull request
Jul 16, 2026
## Summary Version bump + CHANGELOG for 0.1.11. See [CHANGELOG.md](https://github.com/max-sixty/tend/blob/release/CHANGELOG.md#0111) for the full notes. 13 commits since 0.1.10: - Adopter sandbox levers (`sandbox_path`/`sandbox_env`/`sandbox_setup`, #768) - Sandbox `PATH` derived from the runner's own `PATH` (#767) - Invited upstream contributions (#770) - `tend-mention` self-comment no-op skip (#751) - Actionable self-review handling (#762, #775) - `tend-outage` dedup self-heal (#744) - Dropped-cron-tick recovery in `list-recent-runs` (#753) - Drop self-authored attribution sign-offs (#773) - Docs fixes (#776, #771) - `claude_version` bump (#774) ## Test plan - [x] `wt test` (275 passed) - [x] `pre-commit run --all-files` (all hooks passed) - [ ] CI green on this PR > _This was written by Claude Code on behalf of Maximilian Roos_
max-sixty
pushed a commit
to max-sixty/worktrunk
that referenced
this pull request
Jul 17, 2026
Automated nightly regeneration of tend's workflow files, picking up the upstream release. **tend version:** 0.1.10 → 0.1.11 **Notable changes** (consumer-relevant): - Skip no-op `tend-mention` sessions triggered by the bot's own comments — a new pre-mention guard in the generated `tend-mention.yaml` short-circuits before the engagement heuristics (max-sixty/tend#751). - Respond to actionable bot self-reviews instead of exiting as a self-loop: a review the review workflow leaves on its own PR is the bot's reviewer role, so it gets actioned rather than silently skipped (max-sixty/tend#762). - Sandbox: adopter levers to reach inside the Claude-family sandbox, and derive the sandbox `PATH` from the runner's `PATH` (max-sixty/tend#768, max-sixty/tend#767). - `running-in-ci`: permit maintainer-invited upstream contributions, and prohibit self-authored attribution sign-offs (max-sixty/tend#770, max-sixty/tend#773). - Action reliability: self-heal duplicate `tend-outage` issues from concurrent leg failures, and recover dropped cron ticks in list-recent-runs via a previous-run anchor (max-sixty/tend#744, max-sixty/tend#753). Compare: max-sixty/tend@0.1.10...0.1.11 Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The bot occasionally appended a self-authored sign-off to a PR body, e.g.
> _This was written by Claude Code on behalf of @max-sixty_(observed on max-sixty/worktrunk#3427). The PR already comes from the tend bot account, so authorship is unambiguous — the line is noise, and it re-introduces exactly the "Claude" attribution that #759/#760 set out to remove, this time as prose the model writes itself rather than the harness footer those PRs fixed.Root cause
Not template-driven. The strings
behalf/written by/sign-off/attributionappear in no tend template, skill, or harness action (confirmed by greppingshared/,plugins/,claude/,claude-interactive/,codex/), and #760 already emptied the harnessattributionconfig. It's emergent model self-attribution — occasional, not systematic — so there's no template to edit; it needs an explicit don't do this instruction the model reads on every run.Solution
Extend the existing footer prohibition in
plugins/tend-ci-runner/skills/running-in-ci/SKILL.md(Comment Formatting), which already governs the analogous "don't add footers" case, to also cover authorship sign-offs, and to note explicitly that it applies to PR and issue bodies, not just comments.running-in-ciis loaded first in every workflow, so this reaches the PR-creation path without duplicating guidance into a second file.Testing
Skill-text/prompt-compliance change — no code path to unit-test. The reproduction is the linked PR body; the fix is the standing instruction that prevents the model from re-emitting it.
Closes #772 — automated triage