Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…m repos Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
Moderate issues remain in JSON output, fork/PR ref handling, discovery parsing, cleanup, and workflow-run selection.
4 open findings
What changed in this PR
Adds the test-pr skill and helper script for downstream repository integration testing.
Changes:
- Discovers downstream repositories and rewrites workflow references.
- Creates draft test PRs and reports workflow runs.
- Supports cleanup, dry-run modes, and documented usage.
| File | Description |
|---|---|
.github/skills/test-pr/test-downstream.py |
Implements downstream testing automation. |
.github/skills/test-pr/SKILL.md |
Documents the skill, prerequisites, and commands. |
🧠 Review effort: Lite
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… test-pr skill Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…iles Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Use jq line emission for paginated repository discovery - Default --owner to None to allow detected fork owner fallback - Resolve headRefName and owner when --pr is specified from another branch - Route progress and log messages to stderr when --json is enabled Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
mr-cal
left a comment
There was a problem hiding this comment.
What do you think about retrieving the results of the jobs and putting them in the table?
For example, if I update the policy workflow, I'd like to see that all policy workflows pass in the table, without having to open a dozen or more workflows. If it only fails on 1 or 2 repos, it's quicker to know exactly which workflow logs to load.
|
@mr-cal I agree - I need to break it into separate steps though, as it was originally waiting for CI to complete before even making the table. |

This PR introduces the
test-pragent skill in.github/skills/test-pr/to automate downstream CI integration testing across all team repositories.Downstream Test PRs