rootiest/rootiest-ai
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(ship-it): add tea-ci-watch and background CI verification phases #12

Merged
rootiest merged 2 commits from feat/ship-it-ci-watch into main 2026-10-01 00:14:41 +00:00
Conversation 0 Commits 2 Files Changed 5
+165 -4
2 Commits
Author SHA1 Message Date
rootiest d23651850d fix(ship-it): ship tea-ci-watch inside the skill directory
Generate plugin manifests / validate (pull_request) Successful in 20s
Details
Generate plugin manifests / generate (pull_request) Skipped
Details 
The generator copies only known plugin entries into dist/, so a
plugin-root scripts/ directory never reached either target and the skill
depended on a manual ~/.local/bin symlink.

Move the script to skills/ship-it/scripts/, which the skill copytree
already ships to claude-code and agy (plugin and bundle), and have the
skill run it by path relative to its own SKILL.md. Make --check reject
unknown plugin-root entries so a dropped file fails the PR gate.
 2026-09-30 20:13:47 -04:00
rootiest 7620413a25 feat(ship-it): add tea-ci-watch and background CI verification phases
Generate plugin manifests / validate (pull_request) Successful in 23s
Details
Generate plugin manifests / generate (pull_request) Skipped
Details 
Add tea-ci-watch, a blocking watcher for Gitea commit status that polls
the combined status endpoint via `tea api` and exits with a distinct code
per outcome (0 pass, 1 fail, 2 API error, 3 no CI, 124 timeout).

Replace the free-standing CI protocol in the skill with Phase 3 (wait for
PR CI via a single background watcher, then stop for the user to merge)
and Phase 4 (post-merge sync, only when the user says the PR is merged or
asks for a merge). Use `gh pr checks --watch` on GitHub and take the merge
SHA from the PR rather than origin/main.
 2026-09-30 18:19:39 -04:00