Replies: 1 comment
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
In GitHub, to avoid old versions in repos found through search or advanced search, you must search by source code, etc.
Some repos are no longer consistent with the current existing versions, leading to human processing and time-consuming resource consumption to find the required version. Example: Python, Godot, C#, DotNet. Other repos are locked on certain versions.
Adding a possibility to highlight versions used by the development program, possibly the possibility to continue with that repo, will help both to find and reuse the source code faster and to ask questions to the repo owner.
I would propose that in that repo, the continuity of the project over time and the version used can be highlighted, thus allowing a more accurate record of the developers and their involvement, as well as blockages in versions or GitHub repos that are no longer subject to processing due to changes. This way, developers will present themselves more clearly to those interested and can be evaluated more correctly with the degree of involvement and the value invested.
Beta Was this translation helpful? Give feedback.
All reactions