The process to edit a file on github.com must be easier

[vikukush]

With the number of pure documentation repos on github I frequently want to edit a few lines in an .md file.
If I click Edit on a file in the actual repo, there will be a warning that I don't have write access to main branch and must fork it first, but no convenient button to do it for me.
It's not super hard to go back to the repo root and choose the fork option there, but there are clearly much more places where fork button could be added, and overall "editing few lines and sending a PR" should be much more streamlined experience.

[ScribeAegis]

When you want to edit a file on GitHub but don’t have permission to change the original project, you’ll need to make a copy of it first. This is called 'forking.' When you try to edit a file, GitHub will show a message saying you don’t have access and will give you an option to ‘Fork this repository.’ Click on that, and it will create your own copy of the project where you can make the changes. Once you’re done, you can send those changes back to the original project by submitting something called a 'pull request' (PR). This lets the project owner review and potentially merge your changes into the main project.

[dd3vahmad]

That's nice @vikukush, but why don't you create an issue to request for this feature from github.

Sorry can't really type much but you can simply visit this github article page on how to create an issue requesting for a new feature on github.

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