Skip to content

I am writing this for not an absolute solution to most of the issues but to help in remembering git commands. I am uploading this to Github so that I can comeback and check the things for myself later on.

Notifications You must be signed in to change notification settings

socialyadept/GitCheatSheet

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

34 Commits
 
 

Repository files navigation

Everything you need to know for Git

I am writing this for not an absolute solution to most of the issues but to help in remembering git commands. I am uploading this to Github so that I can comeback and check the things for myself later on.

Getting Started

For me these commands are the most important and are basically a crash cheat sheet for most of the common commands used in git. If executed perfectly you won't be needing any other command for work.

1. Initializing a git repository in your current folder

git init

2. Creating a new file

touch <filename>

3. Opening a file using a text editor such as atom

atom <filename>

4. Changing name of a file

mv <previousname> <newname>

Bread and Butter of git

a. Adding files to the repository

git add <filename> <filename> 

or use a '.' to add all of the files in a folder

or use ‘*’ to add file of a certain type such as * .html will add all .html files in a directory

b. Commiting changes

git commit -m "message"

-m is used for not opening a commit file in CLI

5. Checking status

git status

git tracked files means they are added and read by git

untracked files means that they are not added or catered by git

6. Removing a file from commit

git rm --cached <filename>

7. Removing a file from the main directory

rm <filename>

8. Checking git commit's history

git log

9. Visiting back to a commit

git checkout <commit code>

10. Reverting/walking back to a commit from master branch

git revert --no-commit <commit code>..HEAD

Note: you will still have the history of recent updates even if you go back

11. Going back to a commit state from current branch iteratively

git reset HEAD~2

This will move your HEAD back to 2 commits and will stage the committed files that were headed back.

12. Creating a .gitignore file

touch .gitignore

used for ignoring some git files just add names of files inside this .gitignore file and they will vanish

13. For adding a .gitignore file in commit

git add -A

This will add every file including .gitignore for next commit

14. For creating a new branch

git checkout -b <branchname> or git branch <branchname>

15. For deleting a branch

git branch -D <branchname>

16. Check list of branches

git branch

17. Moving to any branch

git checkout <branchname>

18. For merging a branch

git merge <branch_name_other_than_master>

This will automatically create a commit to git as well If you want to merge into master branch -> make sure you are currently in master branch

19. Adding a remote <branch> of a repositiory

git remote add origin master

Remote: here is the remote origin

Add: means we are adding something to a remote rep

Origin: is a name for the push, can be anything else

Master: is a <branch name>, can be any other branch as well

20. Adding a remote link <url> of a repository

git remote add origin <url>

Remote: here is the remote origin

Add: means we are adding something to a remote rep

Origin: is a name for the push, can be anything else

Url: is the url of the reporsitory you want to add to your git bash

Note: For existing repositories first check git pull for checking the current status and then commit changes.

21. Pulling incase the remote repo has unrelated history

Make sure to do this after adding a remote repository to your local computer having different history as compare to your remote repository

git pull origin master --allow-unrelated-histories

22. Pushing everything to the remote repository

git push -u origin master

23. For making a pull request

  1. Go to any github repository for example.
  2. Tap on folk.
  3. Copy the link forked from your copy of the repository.
  4. Open terminal and type.
git clone <url>
  1. Add a new branch:
git checkout -b <branchname>
  1. Make changes, then commit.
  2. Push your changes.
  3. Your repository will automatically show a green button stating compare & pull request in the pull request section
  4. Afterwards use pull request to make a request.

24. Issues when HEAD points to an unborn master branch

You don't have to have a master branch, but you do have to have a "default" branch in any git repository. In a non-bare repository, this is the checked-out branch; in a bare repository, it just means it's the default branch checked out for clones.

This default branch is called HEAD, and must always exist in a valid git repository. If you've removed the branch that HEAD was pointing at, you can reset it to a valid branch with:

git symbolic-ref HEAD refs/heads/<new-main-branch>

25. How to remove the very first commit in git?

The most secure way is to use the update-ref command:

git update-ref -d HEAD

It will delete the named reference HEAD, so it will reset (softly, you will not lose your work) ALL your commits of your current branch. If what you want is to merge the first commit with the second one, you can use the rebase command:

git rebase -i --root

26. Creating an orphan branch?

This is a branch with the same content but without any commit history, and commit your new content on it:

git checkout --orphan <new-branch-name>

Acknowledgments

Muhammad Kumail

Github

Linkedin

Twitter

Facebook

Youtube

About

I am writing this for not an absolute solution to most of the issues but to help in remembering git commands. I am uploading this to Github so that I can comeback and check the things for myself later on.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published