fix(refs): address Copilot second-sweep findings from #56#57
Conversation
- merge-strategy.md: error message now says 'review request(s) (user/team)' instead of 'requested reviewer(s)' so the output matches the code path that counts both users and teams - auto-merge-guide.md: add a pagination note — reviewThreads(first: 100) hits GitHub's per-page maximum but very large PRs can exceed it; point at pageInfo cursor pagination for the edge case Threads: PRRT_kwDOQoDmGs58lGOt, PRRT_kwDOQoDmGs58lGPA Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Code Review
This pull request updates the documentation for auto-merging and merge strategies. Specifically, it adds guidance on handling pagination for GitHub review threads and clarifies an error message to indicate that pending reviews can include both users and teams. I have no feedback to provide as there were no review comments to evaluate.
There was a problem hiding this comment.
Pull request overview
Follow-up documentation tweaks to align reference guidance with the underlying GitHub API/query behavior and the repo’s pending-review check logic.
Changes:
- Update the pending-review status check example message to reflect that both user and team review requests are counted.
- Add a note clarifying that
reviewThreads(first: 100)is GitHub’s per-page maximum and that cursor pagination is needed beyond that.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| skills/github-project/references/merge-strategy.md | Adjusts the example error output to match the check logic counting requested users + teams. |
| skills/github-project/references/auto-merge-guide.md | Documents pagination needs for reviewThreads(first: 100) to avoid missing threads on large PRs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
## Release v2.14.0 Minor release. `.claude-plugin/plugin.json` and `skills/github-project/SKILL.md` frontmatter `metadata.version` were already synced to `2.14.0` on `main` via [#74](#74) — this PR is the empty release marker that closes the v2.13.1 → v2.14.0 window and triggers the signed-tag release. ### Highlights since v2.13.1 - **`agentic-workflows` reference** documenting `gh-aw` and `awf` workflow-as-prompt tooling for autonomous GitHub Actions — new patterns for running AI agents on PRs/issues without bespoke wiring ([#75](#75)). - **AI reviewer pushback patterns** — handling Copilot/Sourcery review comments that disagree with the codebase intent, including when to defer and when to push back ([#66](#66), [#74](#74)). - **PR-merge / branch-protection / CodeQL gotchas** documented, plus auto-detection of allowed merge strategy in the `--delete-branch` snippet so the recipe doesn't break on repos with merge-commit-only policies ([#69](#69), [#71](#71), [#72](#72)). - **GraphQL `Repository.mergeQueue`** for queue detection — replaces a brittle REST probe ([#70](#70)). - **Assessment checkpoints overhaul**: new GH-34/GH-35/GH-36, follow_uses delegation for CodeQL/Scorecard, org_provides for community-health files, broader licence/Dependabot/workflow targets, plus reusable-workflow-pitfalls reference. Multiple false-positive findings demoted to `info` to reduce assessment noise ([#56](#56), [#57](#57), [#58](#58), [#59](#59), [#60](#60), [#61](#61), [#62](#62), [#63](#63), [#64](#64), [#65](#65), [#73](#73)). - **npm distribution** — the skill now also ships via `@netresearch/agent-skill-coordinator` ([#54](#54), [#55](#55)). - **Release pipeline hardening** — dropped the deprecated `with: bump:` block + `workflow_dispatch.bump` input so releases happen exclusively via locally-signed tags, plus SLSA-provenance permissions on the caller ([#52](#52), [#53](#53)). ### Release plan After merge: tag main with a signed annotated tag, push, the `skill-repo-skill` reusable workflow publishes archives + SHA256SUMS with cosign + SLSA attestation, then narrative notes get applied via `gh release edit ... --notes-file`.
Follow-up to Copilot comments on #56 (the follow-up to #55).
Changes
merge-strategy.md: error message now saysreview request(s) (user/team)so the output matches the check's logic (it counts both users and teams).auto-merge-guide.md: add a pagination note —reviewThreads(first: 100)is GitHub's per-page maximum; point at cursor pagination for PRs that might exceed it.Thread IDs resolved after merge