How to Create a New Branch in a Forked Repository using GitHub Web GUI and Submit a PR as the Contributing Guidelines Specifically Say "Create a New Branch for Every PR and Avoid Committing from Master Branch"

[TechieSamosa]

How to Create a New Branch in a Forked Repository using GitHub Web GUI and Submit a PR as the Contributing Guidelines Specifically Say "Create a New Branch for Every PR and Avoid Committing from Master Branch"

I am contributing to a GitHub repository and the contributing guidelines explicitly state to create a new branch for every pull request (PR) and avoid committing from the master branch. I need detailed steps on how to achieve this using the GitHub web interface. Here are my questions:

Creating a New Branch in a Forked Repository

1. Creating a New Branch**:
   • Once I have the repository forked, how can I create a new branch in the forked repository using the GitHub web interface? What are the steps involved?

Making Changes and Committing

2. Making Changes:

   • How do I make changes to files in the new branch using the GitHub web GUI?

3. Committing Changes:

   • How can I commit these changes to the new branch via the web interface?

Submitting a Pull Request (PR)

4. Creating a Pull Request:
   • After committing my changes to the new branch, how do I create a pull request to the original repository? Should I target the master branch or a different branch?
   • What are the steps to ensure my PR is correctly submitted?

Detailed Steps and Best Practices

5. Best Practices:
   • Are there any best practices I should follow when creating branches and submitting PRs to ensure smooth collaboration and code review?

I would appreciate detailed steps and any tips or best practices you can share. Thank you!

---

Steps I've Taken So Far:

1. Forked the repository to my account.
2. Made and committed changes to the new branch.
3. Created a pull request targeting the original repository's master branch that was merged but I was told again "Create a new branch for every PR and avoid committing from master branch"

Issues and Concerns:

• Uncertainty about whether to target the master branch or a different branch for the PR.
• Best practices for naming branches and writing commit messages.
• Ensuring my changes are properly reviewed and merged.

Thanks in advance for your help and guidance!