GET /user/repos with since parameter misses updates on non-default branches

[0xMurage]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

API

Body

The Issue

Currently, API to list user repositories (https://docs.github.com/en/rest/repos/repos?apiVersion=2026-03-10), the since filter seems to rely strictly on the default branch updated_at timestamp. When code is pushed to non-default branches (e.g., a feature or development branch), the repository is entirely omitted from the API response.

Steps to Reproduce

1. Identify a repository where the last activity on the main branch was days ago.
2. Push a new commit to a secondary branch (e.g., dev or feature-xyz) today.
3. Query GET /user/repos?since=[yesterday].
4. Observed Result: The repository is missing from the payload.
5. Expected Result: Because the repository received an update (a new commit/push/branch), it should be included.

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