Skip to content

overlays: GitHub REST collection completeness - #604

Merged
michielbdejong merged 7 commits into
mainfrom
claude/github-rest-completeness
Oct 16, 2026
Merged

michielbdejong merged 7 commits into
mainfrom
claude/github-rest-completeness

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

Completeness overlay for GitHub REST (overlays/APIs/github.com/api.github.com/1.1.4/completeness-920631db…-overlay.yaml). It makes the same declaration as #534's github-issues overlay, from the same GitHub reference:

  • issues: absent: removed, notFound: unavailable, no gone;
  • comments: the same, plus parentAbsent: unavailable.

The paging note is stated as GitHub documents it: the issue after a deleted or transferred one can be skipped, and it still exists.

overlays/tests/test_github_rest_completeness.py:

  • composes with crud-causality v2 in either order with no findings;
  • with v1 it adds nothing to v1's findings;
  • the declaration equals the github-issues one;
  • classify_read outcomes for 301, 404, 410 and 200, and the comments' parent.

README: a row in "Collection completeness". It will conflict by one line with #586's row; whichever lands second takes both.

🤖 Generated with Claude Code

michielbdejong and others added 5 commits October 15, 2026 15:56
The counterpart of the github-issues completeness overlay (#534) for the
full api.github.com document: issues absent removed, notFound unavailable,
no gone; comments the same plus parentAbsent. Same GitHub reference; the
paging sentence says it is the issue after a deleted one that can be
skipped. Tested with crud-causality v2 and v1. Not selected by a catalog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mpleteness

# Conflicts:
#	overlays/README.md
- Merged main: #617's Todoist row joins the table (four overlays with
  this one; five once #586 lands), and the test list names both.
- The "Issues" quote is verbatim now (double quotes, as the docs).
- "Issues are disabled for this repo" is in neither the docs nor the
  pinned OAD: the overlay cites Create an issue's "If issues are disabled
  in the repository, the API returns a 410 Gone status." and marks a read's
  410 and its body as not verified; the test relies on no body text. The
  README notes that #534's published GitHub Issues overlay makes the same
  claim (declaration unaffected: a 410 is unavailable either way).
- Cites Using pagination in the REST API for page-number paging.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michielbdejong
michielbdejong merged commit 6ee2e1a into main Oct 16, 2026
23 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.

1 participant