Git Push Branch to GitLab
Push a Branch to GitLab
Let's try to create a new local branch, and push that to GitLab.
Start by creating a branch, like we did earlier:
Example
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.
Example
git status
On branch update-readme
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." 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:
Example
git add README.md
Check the status
of the branch:
Example
git status
On branch update-readme
Changes to be committed:
(use "git restore --staged ..." to unstage)
modified: README.md
We are happy with our changes. So we will commit
them to the branch
:
Example
git commit -m "Updated readme for GitLab branches"
[update-readme 3361404] Updated readme for GitLab branches
1 file changed, 2 insertions(+)
Now push
the branch
from our local Git repository,
to GitLab, where everyone can see the changes:
Example
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), 364 bytes | 364.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote:
remote: To create a merge request for update-readme, visit:
remote: https://gitlab.com/w3schools-test/hello-world/-/merge_requests/new?merge_request[source_branch]=update-readme
remote:
To https://gitlab.com/w3schools-test/hello-world.git
* [new branch] update-readme -> update-readme
Go to GitLab, Branches, and confirm that the repository has a new branch
:
In GitLab, we can now click the branch, click "Create merge request" to start the process:
Scroll down to see changes:
Note: This comparison shows both the changes from update-readme
and html-skeleton
because we created the new branch FROM html-skeleton
.
If the changes look good, you can go forward, creating a merge request
:
A merge 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 merge
your request yourself:
The merge 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: