Repository navigation
chore: update tend workflows (0.2.8 → 0.2.9) - #683
Merged
Merged
Conversation
Deploying mouseterm with
|
| Latest commit: |
dc16e47
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4bcdb4ec.mouseterm.pages.dev |
| Branch Preview URL: | https://tend-update-workflows.mouseterm.pages.dev |
dormouse-bot
marked this pull request as draft
September 17, 2026 12:03
nedtwigg
marked this pull request as ready for review
September 17, 2026 15:47
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.
Regenerates the nine
.github/workflows/tend-*.yamlfiles against tend 0.2.9(from 0.2.8), which is also the action pin each job now uses.
One functional change reaches the generated YAML. The inline preflight scripts in
tend-notificationsandtend-mentionparsegh --jsonoutput, and a jobenvironment that forces colour made
ghemit ANSI codes inside that JSON body —so the parse saw escape sequences where it expected values. Both preflights now
run
ghwithCLICOLOR_FORCE=0alongsideNO_COLOR=1, becauseghranks aforced colour setting above
NO_COLORand the latter alone did not win(max-sixty/tend#1254). These preflights decide whether the agent job runs at all,
so a misparse there is a skipped or spurious run rather than a cosmetic glitch.
The rest of the diff is the version bump in each header and pin, plus one comment
in
tend-mention-relay.yamlrecording why that job carries noTEND_ENABLEDgate: it boots no agent, and a paused repo's dispatch lands on a
verifyjobthat
TEND_ENABLED=falsealready skips (max-sixty/tend#1258).Upstream also tightened how bundled skills index their
references/files andadded guidance to review a change before the push that opens or fixes a PR
(max-sixty/tend#1253, max-sixty/tend#1259). Those live in the action's skills
rather than in these files, but they change how the bot behaves on this repo from
the moment the pin moves.
No model pins to reconcile —
.config/tend.yamlsets none.Compare: max-sixty/tend@0.2.8...0.2.9