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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
In https://github.com/orgs/community/discussions/187038 it was announced that GitHub would now support disabling pull requests.
The initial idea behind github pull "requests" (I always felt that it was a misnomer) was to signal to some upstream repo owner that they might have been interested in the changes you did in your fork (and could pick that up and merge that in their code).
You never needed PRs for that, but it served some important role in discovering what the community may be doing around your code. Another useful tool for discovery is the forks graph, which I feel got buried deeper in the UI in recent years.
For code maintainers that would prefer not accepting PRs they would have to constantly triage and review, I think it would be nice to have some "forks activity stream" somewhere that shows what's happening in the project's forks.
Beta Was this translation helpful? Give feedback.
All reactions