Git Push Branch to GitHub
Push a Branch to GitHub
Let's create a new local branch, and push that to GitHub.
git checkout -b update-readme Switched to a new branch 'update-readme'
And we make some changes to the README.md file. Just add a new line.
So now we check the
status of the current branch.
git status On branch update-readme Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: README.md no changes added to commit (use "git add" and/or "git commit -a")
We see that
README.md is modified but not added to the Staging Environment:
git add README.md
status of the branch:
git status On branch update-readme Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: README.md
We are happy with our changes. So we will
commit them to the
git commit -m "Updated readme for GitHub Branches" [update-readme 836e5bf] Updated readme for GitHub Branches 1 file changed, 1 insertion(+)
branch from our local Git repository,
to GitHub, where everyone can see the changes:
git push origin update-readme Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 16 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 366 bytes | 366.00 KiB/s, done. Total 3 (delta 2), reused 0 (delta 0), pack-reused 0 remote: Resolving deltas: 100% (2/2), completed with 2 local objects. remote: remote: Create a pull request for 'update-readme' on GitHub by visiting: remote: https://github.com/w3schools-test/hello-world/pull/new/update-readme remote: To https://github.com/w3schools-test/hello-world.git * [new branch] update-readme -> update-readme
Go to GitHub, and confirm that the repository has a new
In GitHub, we can now see the changes and
merge them into the master
branch if we approve it.
If you click the "Compare & pull request", you can go through the changes made and new files added:
Note: This comparison shows both the changes from
html-skeleton because we created the new branch FROM
If the changes look good, you can go forward, creating a
A pull request is how you propose changes. You can ask some to review your changes or pull your contribution and merge it into their branch.
Since this is your own repository, you can
your pull request yourself:
The pull request will record the changes, which means you can go through them later to figure out the changes made.
The result should be something like this:
To keep the repo from getting overly complicated, you can delete the now unused branch by clicking "Delete branch".
An after you confirm that the changes from the previous branch were included, delete that as well: