Repository settings and runners #27

Open
opened 2026-11-19 03:29:47 +00:00 by kathleen · 0 comments
Owner
  • Protect main. Branch rule for main: the status check CI / test (pull_request) is required, and direct pushes and force pushes are off. "Merge when checks succeed" now waits for CI.
  • Bot cycle workflow. The workflow is disabled and its schedule removed (#41). The bot's data arrives through the daily source check instead.
    • To bring it back, Ken sets up a runner with the bot-host label on the bot's machine (DragonKind/DragonKind#6); then the workflow is re-enabled and the schedule uncommented.
    • Six old queued runs couldn't be cancelled through the API (this server's cancel endpoint returns 404). Cancel them in the Actions tab.
  • Ken's repo:
    • DragonKind PR #1 (route model) and #2 (route PDF) are merged. PR #3 carries the latest model and is updated automatically.
    • Update src/pdfRoutes.js from #2's change list.
    • Retire the old GitHub-based AtlasSync and npm run atlas:sync (scripts/sync-atlas.js), which point at GitHub Pages.
  • Hosting the page: on Ken's server.
    • The atlas side: every push to main publishes the built site to the pages branch (#43). The first run succeeded.
    • Ken serves the pages branch at an HTTPS address (DragonKind/DragonKind#8).
    • Set site: in forge.yaml to that address, then rebuild.
  • .gitignore: dropped the /site entry (#41).
  • Daily duplicate runs: added a concurrency group to update-sources.yml (#41).
- [x] **Protect `main`.** Branch rule for `main`: the status check **CI / test (pull_request)** is required, and direct pushes and force pushes are off. "Merge when checks succeed" now waits for CI. - [x] **Bot cycle workflow.** The workflow is disabled and its schedule removed (#41). The bot's data arrives through the daily source check instead. - To bring it back, Ken sets up a runner with the `bot-host` label on the bot's machine (DragonKind/DragonKind#6); then the workflow is re-enabled and the schedule uncommented. - Six old queued runs couldn't be cancelled through the API (this server's cancel endpoint returns 404). Cancel them in the Actions tab. - [ ] **Ken's repo**: - [x] DragonKind PR #1 (route model) and #2 (route PDF) are merged. PR #3 carries the latest model and is updated automatically. - [ ] Update `src/pdfRoutes.js` from #2's change list. - [ ] Retire the old GitHub-based `AtlasSync` and `npm run atlas:sync` (`scripts/sync-atlas.js`), which point at GitHub Pages. - [ ] **Hosting the page: on Ken's server.** - [x] The atlas side: every push to `main` publishes the built site to the `pages` branch (#43). The first run succeeded. - [ ] Ken serves the `pages` branch at an HTTPS address (DragonKind/DragonKind#8). - [ ] Set `site:` in `forge.yaml` to that address, then rebuild. - [x] **`.gitignore`**: dropped the `/site` entry (#41). - [x] **Daily duplicate runs**: added a `concurrency` group to `update-sources.yml` (#41).
kathleen added the infrastructure label 2026-11-19 03:29:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DragonKind/threshing-atlas#27