You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Roadmap and status board for TechMachine, the org's maintenance tooling. It covers the daily health check of every GetTechAPI repo and the scaffold for new satellite repositories.
This issue stays open. The body is the current status. The daily health result lives in #1 (auto-generated; the bot rewrites #1's body each run, so don't edit it by hand). Work items are on Project #2 (Workstream: Automation).
Checks the latest workflow runs on each repo's branches in machine/repos.json, plus the public endpoints. Rewrites #1 and mentions @Seungpyo1007 when the problem set changes. Treats cancelled/timed_out as problems, since that's how jobs killed at a time limit report.
python -m machine.new_satellite … creates a new data repo in the game-catalog layout, with summary.json and history.json for the TechAPI homepage. It only creates files; org settings are done by hand (add main to the github-pages environment).
Health: 1 problem, TechEngine main · weekly-refresh (5 failed or cancelled runs). TechEngine #96 fixed its PR target; the 2026-09-28 run will show whether the failures are gone.
Branches: develop (default) → main releases, same git-flow as TechAPI.
Goals (milestone "Org tooling (2026)")
Add org hygiene checks to the daily report. This turns the 2026-09-27 audit into a daily check: PRs missing from Project feat(health): mention the maintainer when the problem set changes #2, board items with empty fields, open tracker issues with a closing link, PRs merged without green CI.
Include the .github repo and the TechAPI trackers (Org health report #1, #295-#297) in the report.
Keep Org health report #1 useful: one line per problem, linking to the failing run.
Purpose
Roadmap and status board for TechMachine, the org's maintenance tooling. It covers the daily health check of every GetTechAPI repo and the scaffold for new satellite repositories.
This issue stays open. The body is the current status. The daily health result lives in #1 (auto-generated; the bot rewrites #1's body each run, so don't edit it by hand). Work items are on Project #2 (Workstream: Automation).
What TechMachine does
machine/health.py,.github/workflows/health.yml(daily)machine/repos.json, plus the public endpoints. Rewrites #1 and mentions @Seungpyo1007 when the problem set changes. Treatscancelled/timed_outas problems, since that's how jobs killed at a time limit report.machine/new_satellite.py,machine/satellite_template/python -m machine.new_satellite …creates a new data repo in the game-catalog layout, withsummary.jsonandhistory.jsonfor the TechAPI homepage. It only creates files; org settings are done by hand (addmainto thegithub-pagesenvironment).tests/,.github/workflows/test.ymlWatched repos (
machine/repos.json): TechAPI (develop, main), TechEngine (main), game-catalog (develop, main), cpu-engineering-samples (develop, main).Current status (2026-09-27)
main· weekly-refresh (5 failed or cancelled runs). TechEngine #96 fixed its PR target; the 2026-09-28 run will show whether the failures are gone.develop(default) →mainreleases, same git-flow as TechAPI.Goals (milestone "Org tooling (2026)")
.githubrepo and the TechAPI trackers (Org health report #1, #295-#297) in the report.Links