Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows
chore: update tend workflows (0.1.10 → 0.1.11) (#3500)
Worktrunk Bota1332d46bd28
diff --git a/.github/workflows/tend-ci-fix.yaml b/.github/workflows/tend-ci-fix.yamlindex f62c9c541..1df6a4b27 100644--- a/.github/workflows/tend-ci-fix.yaml+++ b/.github/workflows/tend-ci-fix.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-mention.yaml b/.github/workflows/tend-mention.yamlindex 11431a9eb..2f7680573 100644--- a/.github/workflows/tend-mention.yaml+++ b/.github/workflows/tend-mention.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,@@ -62,6 +62,29 @@ jobs:exit 0fi+ # Skip the bot's own comments before anything else. The Bot-type+ # check below only catches GitHub App / Bot accounts; our own bot is a+ # PAT-based User account, so its comments would otherwise fall through+ # to the engagement heuristics (bot-authored issue, "bot has prior+ # comments") and spin up a handle job the prompt's self-loop guard+ # then exits silently — pure waste. There is no legitimate+ # self-summons: a bot comment that quotes a prior @-mention would+ # re-match the mention check below and escape an after-placed guard,+ # so this runs *before* the mention check. Covers issue_comment and+ # pull_request_review_comment (both carry comment.user.login). Fires+ # on, e.g., the monthly tracking-issue rollover where the bot posts+ # evidence-gist links on its own issue. Scoped to comments on+ # purpose: the pull_request_review *submission* event is deliberately+ # left out, since a review the bot leaves on its own PR is its+ # reviewer role (the prompt is told to action it), not a self-loop.+ # The only self-review skip is the terminal empty-body APPROVED gate+ # below.+ if { [ "$EVENT_NAME" = "issue_comment" ] || [ "$EVENT_NAME" = "pull_request_review_comment" ]; } \+ && [ "$COMMENT_AUTHOR" = "worktrunk-bot" ]; then+ echo "should_run=false" >> "$GITHUB_OUTPUT"+ exit 0+ fi+if [ -n "$COMMENT_BODY" ] && printf '%s\n' "$COMMENT_BODY" | grep -qF '@worktrunk-bot'; thenecho "should_run=true" >> "$GITHUB_OUTPUT"exit 0@@ -156,6 +179,7 @@ jobs:GITHUB_TOKEN: ${{ secrets.TEND_BOT_TOKEN }}EVENT_NAME: ${{ github.event_name }}COMMENT_BODY: ${{ github.event.comment.body || github.event.review.body }}+ COMMENT_AUTHOR: ${{ github.event.comment.user.login }}COMMENT_AUTHOR_TYPE: ${{ github.event.comment.user.type }}ISSUE_BODY: ${{ github.event.issue.body }}ISSUE_OR_PR_NUMBER: ${{ github.event.issue.number }}@@ -252,7 +276,7 @@ jobs:|| (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@worktrunk-bot')&& format('A review was submitted on PR #{0} that mentions you ({1}, review ID {2}). Read the review and full context, then respond. If changes were requested, make them, commit, and push.', github.event.pull_request.number, github.event.review.html_url, github.event.review.id))|| (github.event_name == 'pull_request_review'- && format('A review was submitted on a PR where you previously participated (PR #{0}, {1}, review ID {2}). Read the review and full context. If the review requests changes or asks questions, respond appropriately. If the review approves or is between humans, exit silently.', github.event.pull_request.number, github.event.review.html_url, github.event.review.id))+ && format('A review was submitted on a PR where you previously participated (PR #{0}, {1}, review ID {2}). Read the review and full context. If it requests changes or asks questions, respond appropriately — including when you authored the review: a review your review workflow left on your own PR is your reviewer role speaking, not a self-loop, so action it. Exit silently for a plain approval, a review with no actionable content, or one between other participants.', github.event.pull_request.number, github.event.review.html_url, github.event.review.id))|| (contains(github.event.comment.body, '@worktrunk-bot')&& format('You were mentioned in a comment ({0}). Read the full context and respond. If changes are requested, make them, commit, and push.', github.event.comment.html_url))|| format('A user commented on an issue/PR where you previously participated ({0}). Read the full context. Only respond if the comment is directed at you, asks a question you can help with, or requests changes you can make. If the conversation is between other participants, exit silently.', github.event.comment.html_url)diff --git a/.github/workflows/tend-nightly.yaml b/.github/workflows/tend-nightly.yamlindex c0898dd47..ba75bcbcd 100644--- a/.github/workflows/tend-nightly.yaml+++ b/.github/workflows/tend-nightly.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-notifications.yaml b/.github/workflows/tend-notifications.yamlindex b2f5a46d2..da23bc0e8 100644--- a/.github/workflows/tend-notifications.yaml+++ b/.github/workflows/tend-notifications.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-review-runs.yaml b/.github/workflows/tend-review-runs.yamlindex d23326b71..2f1a1f428 100644--- a/.github/workflows/tend-review-runs.yaml+++ b/.github/workflows/tend-review-runs.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-review.yaml b/.github/workflows/tend-review.yamlindex d85bdcef9..1ef1e8cca 100644--- a/.github/workflows/tend-review.yaml+++ b/.github/workflows/tend-review.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-triage.yaml b/.github/workflows/tend-triage.yamlindex 93283ac78..95b46e377 100644--- a/.github/workflows/tend-triage.yaml+++ b/.github/workflows/tend-triage.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,diff --git a/.github/workflows/tend-weekly.yaml b/.github/workflows/tend-weekly.yamlindex 4edc78a8d..9a9965e96 100644--- a/.github/workflows/tend-weekly.yaml+++ b/.github/workflows/tend-weekly.yaml@@ -1,4 +1,4 @@-# Generated by tend 0.1.10. Regenerate with: uvx tend@latest init+# Generated by tend 0.1.11. Regenerate with: uvx tend@latest init## Do not edit this file directly — it will be overwritten on regeneration.# To customize behavior, edit the relevant skill (for example,