Search for code in repositories I have write access to

[effigies]

Select Topic Area

Product Feedback

Body

One thing that would be useful is the ability to look for code in any repository I have write access to. I thought the owner: selector might do this, but it only seems to find things under my user. This is a decent proxy if I have an up-to-date fork, but also includes lots of repositories that I have only contributed to.

The motivating use case is API deprecations. When a deprecation comes up, it would be nice to be able to quickly find everywhere that I can do something about it.

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

[look]

Hi @effigies, thanks for the feedback. While there is no search syntax specifically for this, the default operation for search without owner: or repo: qualifiers is to limit your search to public repositories plus those you have read access to. This might get you close enough.

I would like to add a search syntax for non-public repositories, but we haven't been able to implement that yet.

[effigies]

I'm actually not interested in private repositories at all. I wanted search for something like "pkgutil.find_loader", which is a deprecated Python interface. But it's not very interesting to me if it shows up in a public dataset that I have no responsibility for. Write access is mostly a proxy for "is it my fault if someone's code breaks because I haven't fixed this?".

[look]

I see, thanks for clarifying. I'll pass this use case on to the team.

[LandazuriPaul]

Hello!

I would also be interested in a filter that says: "look only within the repositories where I'm a collaborator". It seems that GitHub already has this information since it can be accessed in this settings page: https://github.com/settings/repositories.

Similarly, I think that we could have filters for:

• watched repositories: GitHub exposes the list here: https://github.com/watching
• subscribed repositories: GitHub exposes the list under the repositories filter here: https://github.com/notifications/subscriptions.

The motivation behind these 3 proposed filters is that we should be able to quickly look up something that we know is happening in these different categories. But currently, if we don't remember exactly the name or the owner of the repository we watched/commented on or collaborated on 1 month ago, it's quite faffy to get to it. Ideally, we could even have a filter that includes all 3 of the above. 🙂

[look]

Thanks for these suggestions. Seems like a useful use case, I shared this post with the team.

[dogsbody]

@look A great example of this and the reason I found this discussion is the notification I had from GitHub yesterday regarding artifact actions v3 will being deprecated.

I am a member of 11 organisations with probably over 100 repos across them. I have absolutely no idea which repo is using artifact actions v3! 😅

The search functionality above would really help me find this 👍

Thank you for listening