Creating a pull request without a feature branch

In Git, a version control system used for tracking changes in computer files and coordinating work among multiple people, the pull request (PR) is a key component. A pull request in Git is essentially a request to merge one branch into another; by definition, it involves two distinct branches. This guide clarifies why it's not possible to create a pull request directly on the main branch without involving another branch and offers best practices for initiating a proper pull request.

Understanding the branch-based nature of pull requests

A pull request necessitates the existence of at least two branches: a source branch containing the proposed changes and a target branch where these changes are intended to be merged. Typically, the main branch serves as the target because it represents the stable, production-ready state of the project. When developers wish to add new features or make updates, they create a separate branch (often called a feature branch) from the main. This separation ensures that the main branch remains stable and unaffected by ongoing developments until they are fully reviewed and approved.

What happens if you try to bypass the feature branch?

Attempting to create a pull request without a feature branch would mean making and committing changes directly to the main branch. This action contravenes the fundamental principles of pull requests for several reasons:

• Lack of isolation: Without a separate branch, the changes impact the main branch immediately upon commit, eliminating the protective buffer that a feature branch offers.
• Review complications: Conducting a review without this separation is challenging because the changes are already applied to the main branch, complicating rollback procedures if problems are found.

Best practices for initiating pull requests

To maintain the integrity of the development workflow and ensure that the main branch remains stable, follow these best practices when creating pull requests:

1. Always create a feature branch: Regardless of the size of the change, start by creating a feature branch from the main branch. This approach isolates your changes and keeps the main branch clean.

   Terminal

   git checkout -b new-feature
   
   

2. Make, commit, and push changes: Implement your changes in the feature branch and use the following commands to add, commit, and push the changes to the remote repository:

   Terminal

   git add .
   git commit -m "Detailed commit message"
   git push origin new-feature
   
   

3. Open the pull request: Navigate to your repository on GitHub, and you'll find an option to create a pull request for your newly pushed branch. Initiate the pull request by comparing the feature branch against the main branch.

4. Utilize review tools: Tools like Graphite's PR inbox can enhance the management and visibility of pull requests, especially when handling multiple feature branches.

Summary

While it might seem convenient to bypass the creation of a feature branch for small changes or quick fixes, adhering to the best practices of Git workflow not only prevents potential errors but also supports a structured and manageable development process.