Undocumented field 'verified_at' breaks the rate limit

[algvozdev]

Select Topic Area

Bug

Body

I am using GitHub api and yesterday I found out that compare two commits request https://docs.github.com/en/rest/commits/commits?apiVersion=2022-11-28#compare-two-commits returns an undocumented field verified_at for verified commit. That field breaks GitHub api rate limit because contains the current response time and after that every new request has the new generated etag value.

Request:
curl -s -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" -H 'Authorization: token <some secret token>' https://api.github.com/repos/<MY_ORGS>/<MY_REPO>/compare/master...bab4146b9e7c7885d5608f9db5b8b6352d5825f4

Part of response with field verified_at:

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

[patjlm]

We're facing the same on the commit APIs (single, list. pull-request)
https://api.github.com/repos/OWNER/REPO/commits/REF
https://api.github.com/repos/OWNER/REPO/commits
https://api.github.com/repos/OWNER/REPO/pulls/PRID/commits