Add open-Knots-PRs triage view: source/label/ready filters + daily ACK refresh#6
Merged
Conversation
kwsantiago
changed the title
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.
Adds an open-PRs triage view and richer filters so all open
bitcoinknots/bitcoinPRs, not just the ones referenced in a spec, can be triaged and shortlisted for a release. Requested in the Knots dev discussion.View
github.list_open_prs(repo)— enumerates all open (non-draft) PRs via the API (paginated, token-aware)./api/knots-prs, baked todata/__knots__.jsonfor the static site. Of the 50 open PRs, 33 aren't in the spec at all, so this surfaces work the spec view can't.Filters
k###/g###).high prioritylabel makes the "mark high priority" workflow work with no new mechanism: label on GitHub, filter here.Freshness
Deploy
BOSUN_CACHE_TTLlowered 3 days → 1 day, so each daily run re-fetches ACKs for every open PR. New PRs already appeared daily; rate-limited fetches are caught and retried next run.Design
ACK/tACK data stays fully dynamic (fetched live from the API, classified in
ack.py, re-baked each deploy). Nothing about review status touches the spec file, which keeps its single job as the build recipe.Docs
README links the live instance, the default spec source, and the proposed DAG-native model, and documents the new view + filters.
The live site defaults to the Knots-PR view; switching back to the spec is a one-line change.