API to get a tree returns 404 for an empty tree even though it exists

[divdavem]

Select Topic Area

Bug

Body

Hi,

I am starting this discussion to report a bug with the API to get a tree when the tree is empty.

Here is a sample repository where I reproduced the issue:
https://github.com/divdavem/empty-repository

It contains, in its master branch, a simple commit that contains no file.
The sha of the commit is 3fb7891cf06183a3055f1a1a639b50d069a9f036.

If I call the API with the following URL: https://api.github.com/repos/divdavem/empty-repository/git/trees/master?recursive=1
I am getting the following 404 response:

{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest/git/trees#get-a-tree",
  "status": "404"
}

This is wrong: the master branch exists, it just contains no file. I would instead expect the following 200 response:

{
  "sha": "3fb7891cf06183a3055f1a1a639b50d069a9f036",
  "url": "https://api.github.com/repos/divdavem/empty-repository/git/trees/3fb7891cf06183a3055f1a1a639b50d069a9f036",
  "tree": [],
  "truncated": false
}

It just contains an empty array in the tree, but otherwise looks like what I get if I call the API with the following URL: https://api.github.com/repos/divdavem/empty-repository/git/trees/readme?recursive=1:

{
  "sha": "526bb721ca80fe0169893d0d7b4d436479dea61a",
  "url": "https://api.github.com/repos/divdavem/empty-repository/git/trees/526bb721ca80fe0169893d0d7b4d436479dea61a",
  "tree": [
    {
      "path": "README.md",
      "mode": "100644",
      "type": "blob",
      "sha": "e69de29bb2d1d6434b8b29ae775ad8c2e48c5391",
      "size": 0,
      "url": "https://api.github.com/repos/divdavem/empty-repository/git/blobs/e69de29bb2d1d6434b8b29ae775ad8c2e48c5391"
    }
  ],
  "truncated": false
}

Could you please fix this issue? Or did I miss something?

Thank you in advance!

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