Skip to content

ci: add kanban + PR-status caller workflows#19

Merged
LukasWodka merged 1 commit into
mainfrom
ci/kanban-and-pr-workflows
May 19, 2026
Merged

ci: add kanban + PR-status caller workflows#19
LukasWodka merged 1 commit into
mainfrom
ci/kanban-and-pr-workflows

Conversation

@saadqbal

@saadqbal saadqbal commented May 19, 2026

Copy link
Copy Markdown
Collaborator

Summary

Splits the CI portion out of #15. These caller workflows live on `develop` (added in #5, #6, #9, #10) but never reached `main`.

  • `pull_request_template.md`
  • `workflows/add-to-kanban.yml` — auto-add new issues/PRs to project 2
  • `workflows/customer-priority-bump.yml` — bump priority on customer label
  • `workflows/kanban-closure-routing.yml` — route closed work to the correct column
  • `workflows/set-pr-status.yml` — set PR status on the board
  • `workflows/stale-backlog.yml` — auto-close stale backlog issues
  • `workflows/wip-limit-check.yml` — enforce per-column WIP limits

All delegate to the org-wide reusable workflows; no new logic in this repo.

Closes #17. Supersedes the CI portion of #15.

Open question for review

Worth confirming whether every workflow is appropriate for a docs/quickstart repo. `wip-limit-check` and `customer-priority-bump` were designed for engineering work and may be noise here. Happy to drop either during review.

Test plan

  • PR template renders on this PR
  • `add-to-kanban` adds this PR (or a fresh issue) to project 2 on tracebloc org
  • `set-pr-status` sets a column when this PR is opened
  • `stale-backlog` runs on schedule without errors (check Actions tab after merge)
  • Confirm decision on `wip-limit-check` + `customer-priority-bump`

🤖 Generated with Claude Code


Note

Medium Risk
Workflow-only change, but it affects repo governance: issues/PRs will be auto-added/routed in a GitHub Project, can auto-close stale issues, and relies on a PROJECTS_KANBAN_TOKEN secret which could fail or mis-route work if misconfigured.

Overview
Adds a new .github/pull_request_template.md to standardize PR metadata, testing, and review checklist.

Introduces multiple GitHub Actions workflows to automate repo triage: auto-add issues/PRs to the org kanban project, set PR board status, route closed issues/PRs, bump priority on customer labeling, enforce WIP limits, and schedule a stale-issue process that labels and closes inactive issues (PRs exempt). These mostly delegate to reusable org-wide workflows and add a required PROJECTS_KANBAN_TOKEN secret for project access.

Reviewed by Cursor Bugbot for commit 990b6ab. Bugbot is set up for automated code reviews on this repo. Configure here.

Splits the CI portion out of #15. These caller workflows live on
develop (added in #5, #6, #9, #10) but never reached main.

- pull_request_template.md
- workflows/add-to-kanban.yml — auto-add new issues/PRs to project 2
- workflows/customer-priority-bump.yml — bump priority on customer
  label
- workflows/kanban-closure-routing.yml — route closed work to the
  correct column
- workflows/set-pr-status.yml — set PR status on the board
- workflows/stale-backlog.yml — auto-close stale backlog issues
- workflows/wip-limit-check.yml — enforce per-column WIP limits

All delegate to the org-wide reusable workflows. No new logic in this
repo.

Closes #17.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@LukasWodka

Copy link
Copy Markdown
Contributor

👋 Heads-up — Code review queue is at 18 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

@saadqbal saadqbal self-assigned this May 19, 2026
@LukasWodka LukasWodka merged commit 1cd8f26 into main May 19, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Land kanban/PR-status workflows on start-training

2 participants