Distinguish forks related to new project branches, from ones inherent to Pull Requests #64779
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi everyone!
Recently I've tried to find some search filter to find out which forks of a project were created to continue the development aside of the original one, discarding forks that were created just for Pull requests.
A practical example:
Is any similar feature already available?
If not, what about implementing a new feature to make this distinction easier?
Probably a new search filter would be enough: "forks mentioned in a PR".
It would be even better with the possibility to highlight forks where the "About" message and/or the Readme file content differs from the original project.
Beta Was this translation helpful? Give feedback.
All reactions