Two simple ways to rebase your development repo on github before your renew your work


As you work on a new feature in your Git repository, you might find that changes are being made to the master branch that you need to incorporate into your feature branch. In this case, you have two options to rebase your feature branch with the latest changes from the master branch: you can do it locally using Git, or you can do it on the GitHub page using pull requests.

Method 1: Rebase locally using Git

Step 1: Checkout the feature branch

First, make sure you’re on the feature branch that you want to rebase with the master branch. You can do this by using the git checkout command:

git checkout feature-branch

Step 2: Fetch the latest changes from the master branch

Next, you need to fetch the latest changes from the master branch. This will allow you to see any changes that have been made since you started working on your feature branch. You can do this using the git fetch command:

git fetch origin master

This will fetch the latest changes from the master branch on the remote repository named “origin”.

Step 3: Rebase your feature branch with the latest changes from the master branch

Now that you have the latest changes from the master branch, you can rebase your feature branch with those changes. You can do this using the git rebase command:

git rebase origin/master

This will apply the latest changes from the master branch to your feature branch, one commit at a time. If there are any conflicts between your feature branch and the master branch, Git will prompt you to resolve them before continuing.

Step 4: Push the updated feature branch to the remote repository

Once you’ve resolved any conflicts and rebased your feature branch with the latest changes from the master branch, you need to push your updated feature branch to the remote repository so that others can see and work with your changes. You can do this using the git push command:

git push origin feature-branch

This will push the updated feature branch to the remote repository named “origin”.

Step 5: Merge the feature branch back into the master branch

Once you’re finished working on your feature branch and have successfully rebased it with the latest changes from the master branch, you can merge your feature branch back into the master branch. You can do this using the git merge command:

git checkout master
git merge feature-branch

This will merge the changes from your feature branch into the master branch, and create a new merge commit. You can then push the updated master branch to the remote repository using the git push command.

Method 2: Rebase on GitHub using pull requests

Step 1: Create a pull request for your feature branch

The first step is to create a pull request for your feature branch. This will allow you to merge your changes into the master branch once they have been approved. To do this, go to the GitHub repository and click on the “New pull request” button. Then select your feature branch as the “compare” branch and the master branch as the “base” branch.

Step 2: Review the pull request

Once you’ve created the pull request, you can review the changes and make any necessary adjustments. If you need to make changes to your feature branch, you can do so locally and then push the changes to the remote repository.

Step 3: Rebase your feature branch with the latest changes from the master branch

Before merging your changes into the master branch, you’ll want to rebase your feature branch with the latest changes from the master branch. You can do this using the “Rebase and merge” option in the pull request interface. This will apply the latest changes from the master branch to your feature branch and then merge the changes into the master branch.

Step 4: Resolve any conflicts

If there are any conflicts between your feature branch and the master branch, you’ll need to resolve them before you can merge your changes. GitHub will notify you of any conflicts and provide tools to help you resolve them.

Step 5: Merge your changes into the master branch

Once any conflicts have been resolved, you can merge your changes into the master branch using the “Merge pull request” button in the pull request interface. This will create a new merge commit that incorporates the changes from your feature branch into the master branch.

Step 6: Delete the feature branch

Once you’ve merged your changes into the master branch, you can delete your feature branch. This will help keep your repository clean and make it easier to manage your branches in the future. You can do this using the “Delete branch” button in the pull request interface.


Author: robot learner
Reprint policy: All articles in this blog are used except for special statements CC BY 4.0 reprint policy. If reproduced, please indicate source robot learner !
  TOC