Repository.databaseId is a 32-bit Int and new repo ids are already past 1.1 billion #203675
Unanswered
me93-ghb
asked this question in
Apps, API and Webhooks
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
API
Body
Repository.databaseIdis typedInt, which the GraphQL spec pins to 32-bit signed, so the ceiling is 2147483647.New repos are currently getting ids around 1.15 billion (one created this summer got 1148214569), a bit over halfway there. Rough extrapolation (especially with more AI development) suggests that's only years away. When a repo id crosses the line, a spec-compliant server has no choice but to error on the field.
Other types already handle this:
fullDatabaseId: BigIntexists onIssue,PullRequest, review comments and the ProjectV2 types, whose ids blew past Int long ago.RepositoryandUsernever got it. Adding it there too would let people migrate before it becomes urgent.REST is unaffected since it's plain JSON numbers. This is only about the GraphQL type.
All reactions