Private-repo git over HTTPS returns 404 with stateless App installation token; classic token works

[abhi-k-goswami]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

Our GitHub App (owlkeep-broker-akg, installed on the personal account abhi-k-goswami) mints a token for one private repo, abhi-k-goswami/owlkeep-broker-test (repo ID 1411376027): POST /app/installations/{id}/access_tokens with repository_ids [1411376027] and permissions contents: write, pull_requests: write, metadata: read.

On 27 Oct 2026, with the default stateless format:

• REST calls on the repo return 200 (contents, commits, refs).
• GET https://github.com/abhi-k-goswami/owlkeep-broker-test.git/info/refs?service=git-upload-pack with Basic x-access-token: returns 404, from both git 2.54 and curl. The REST tarball download also returns 404 at codeload.
• On a public repo, git accepts the same token sent up front, and a made-up token gets 401. So the endpoint does check the token.
• GitHub Actions' GITHUB_TOKEN, also stateless, clones this account's private repos over git without problems. Only tokens minted for our App fail.

The same mint with X-GitHub-Stateless-S2S-Token: disabled: clone, push and PR creation all succeed.

Failing request: x-github-request-id D2A1:3468D7:3E27C0:596406:6AE052A5, 2026-10-27 07:28:39 UTC (edge region southeastasia). App ID and installation ID on request.

Is this expected? What should we change so git works with stateless tokens before the header stops working on 30 Nov 2026?

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐