ci: open nightly-failure issues with prql-bot PAT#5770
Merged
Conversation
The nightly-failure issue was created with the default GITHUB_TOKEN, whose events do not cascade to other workflows — so tend-triage never ran on it. Switch to PRQL_BOT_GITHUB_TOKEN so triage fires. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The previous commit switched nightly-failure issues to be opened by prql-bot so the event would cascade to tend-triage, but tend-triage's own filter skips all prql-bot-authored issues. Narrow that filter to still allow issues labeled `github_actions` (the nightly-failure label) through. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Closed
Member
|
the first one is generated by |
Collaborator
Author
|
Filed max-sixty/tend#149 for the header-guidance request. On the local tend-triage.yaml edit in this PR: happy to revert it once tend supports the label-based filter upstream, but leaving it for now so the nightly gets triaged in the meantime — let me know if you'd rather drop it and wait. |
Member
|
drop the first change |
Merged
2 tasks
This reverts commit ece20b8.
Collaborator
Author
|
Dropped the tend-triage.yaml edit (reverted in 1a8649c) — will wait for the upstream fix in max-sixty/tend#149. The tests.yaml token change remains. |
max-sixty
pushed a commit
to max-sixty/tend
that referenced
this pull request
Apr 7, 2026
… YAML (#150) Closes #149. Extends the generated-workflow header with explicit guidance pointing downstream maintainers at repo-local skills or upstream issues, rather than hand-editing the YAML (which gets silently reverted on the next `uvx tend init`). Motivated by [PRQL/prql#5770](PRQL/prql#5770), where a triage-filter fix went into the generated workflow file. New header (applied to all generated workflows): ``` # Generated by tend. 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 in this repo's # .claude/skills/ directory, or open an issue at # https://github.com/max-sixty/tend/issues for changes that need to # happen upstream in the tend-ci-runner plugin. ``` ## Test plan - [x] `cd generator && uv run pytest` (112 passed) - [x] `uvx tend init` regenerates all 8 workflows with the new header --------- Co-authored-by: tend-agent <270458913+tend-agent@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.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
2 participants
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.
Summary
Fixes the gap @max-sixty flagged in #5769: the nightly-failure issue was opened via the default
GITHUB_TOKEN, whose events do not cascade to other workflows, sotend-triagenever ran on it.Two small changes:
.github/workflows/tests.yaml— create the nightly-failure issue withPRQL_BOT_GITHUB_TOKENinstead ofGITHUB_TOKEN, so theissues: openedevent cascades..github/workflows/tend-triage.yaml— the existing filtergithub.event.issue.user.login != 'prql-bot'would still skip the newly-bot-authored issue, so narrow it to allow issues labeledgithub_actions(the label set by.github/nightly-failure.md).Note:
tend-triage.yamlis normally regenerated byuvx tend init; I added a comment flagging the local customization so it isn't silently clobbered on regen. If there's a better upstream place for this, happy to move it.Test plan
prql-bot, which triggerstend-triage.github_actionsprql-bot issues (e.g. devcontainer bumps) continue to be skipped by triage.🤖 Generated with Claude Code