ci: route PRs to workstream trackers and stop per-PR tracker comments - #298
Merged
Merged
Conversation
#1 had 329 comments and 215 linked PRs because every data PR closed #1 and got a tracker comment. Route by kind instead: releases and dumps -> #1, new records -> #295, fixes -> #296, ci/app -> #297, site -> #19, and keep a tracker the author already linked. The automatic tracker comment now only fires for release PRs. The data summary counts all 12 categories. Refs #297
github-actions
Bot
added
the
documentation
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
1 participant
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.
Implements the tracker split from #1 (2026-09-27).
Routing (
pr-metadata, theCloses #Nline)base: main),chore(dump…), or onlysite/public/v1changesdata+ (bugor title starts withfix)data(otherwise)siteci/appwith nothing aboveCloses #Nfor one of these trackers, it's left alone.Closeslink. That per-PR comment is why TechAPI dataset roadmap and status: all categories (1989-2026) #1 grew to 329 comments.Security: only the routing table and comment condition change. No checkout, and PR text is never interpolated into
run:(pull_request_targetrule, rules §10). The embedded script passednode --check.Since
pull_request_targetuses the base branch's workflow, the new routing takes effect after merge. I'll check it on the next data, fix and CI PRs.Closes #297