Pets and cattle problem on github

[Harvie]

Select Topic Area

Product Feedback

Body

Hello,
i am working on many projects on github and i have troubles separating pet and cattle repositories. I'll give you example:

• Pets: My projects (original or forks) that i feel being responsible for individualy that i want to keep maintaining and developing further
• Cattle: Random forks of other people's projects (from github or not) that i only have on my github just to prepare patches or pull requests without any plans for long-term maintenance or "petting". This might be just some one-shot fix project in library that is needed by one of my pets.

Right now when i open my github, my pets and cattle are running randomly mixed in single pasture. I'd like some way to distinguish between these. So i can check all my pets every week, to see how they're doing, while knewing cattle is just living their lifes without my help.

I was considering creating separate github organization for my cattle, or "pinning" my pets. But that does not really work for me, since i don't want to pin all pet repositories nor do i want pet-related cattle fixes to reside in separate organisation.

I would really like to see some feature that would allow me to set my github repos either as "pet" or "cattle". So it is immediately obvious to me and other people whether i am planning to maintain the repo long-term or if it's just temporary repo where i act as mere contributor.

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