In short, how does Git work?

4 min read
Hakan Budak
Mar 23, 2023

usage: git branch [<options>] [-r | -a] [ — merged] [ — no-merged]
or: git branch [<options>] [-l] [-f] <branch-name> [<start-point>]
or: git branch [<options>] [-r] (-d | -D) <branch-name>…
or: git branch [<options>] (-m | -M) [<old-branch>] <new-branch>
or: git branch [<options>] (-c | -C) [<old-branch>] <new-branch>
or: git branch [<options>] [-r | -a] [ — points-at]
or: git branch [<options>] [-r | -a] [ — format]

Generic options
-v, — verbose show hash and subject, give twice for upstream branch
-q, — quiet suppress informational messages
-t, — track set up tracking mode (see git-pull(1))
-u, — set-upstream-to <upstream>
change the upstream info
— unset-upstream unset the upstream info
— color[=<when>] use colored output
-r, — remotes act on remote-tracking branches
— contains <commit> print only branches that contain the commit
— no-contains <commit>
print only branches that don’t contain the commit
— abbrev[=<n>] use <n> digits to display object names

Specific git-branch actions:
-a, — all list both remote-tracking and local branches
-d, — delete delete fully merged branch
-D delete branch (even if not merged)
-m, — move move/rename a branch and its reflog
-M move/rename a branch, even if target exists
-c, — copy copy a branch and its reflog
-C copy a branch, even if target exists
-l, — list list branch names
— show-current show current branch name
— create-reflog create the branch’s reflog
— edit-description edit the description for the branch
-f, — force force creation, move/rename, deletion
— merged <commit> print only branches that are merged
— no-merged <commit> print only branches that are not merged
— column[=<style>] list branches in columns
— sort <key> field name to sort on
— points-at <object> print only branches of the object
-i, — ignore-case sorting and filtering are case insensitive
— format <format> format to use for the output

  • Create a “repository” (project) with a git hosting tool (like Bitbucket)
  • Copy (or clone) the repository to your local machine
  • Add a file to your local repo and “commit” (save) the changes
  • “Push” your changes to your main branch
  • Make a change to your file with a git hosting tool and commit
  • “Pull” the changes to your local machine
  • Create a “branch” (version), make a change, commit the change
  • Open a “pull request” (propose changes to the main branch)
  • “Merge” your branch to the main branch

Good week everyone

Thank you very much for reading.


From the blog

The latest industry news, interviews, technologies, and resources.
No items found.

Get Top landing pages by session

You don't need worry about performance changes or missing opportunities, in one email, heybooster Google Analytics Weekly Report summarizes all.