Git Cheat Sheet

Init new Local GIT Repo

Setup a repo folder

cd to the git repo location, log in as git and create a folder for the new git project repository

cd /srv/git
su git
mkdir <project>.git

Init the repo

cd into the <project>.git folder

cd <project>.git
git init --bare
mkdir <project>.git

Local GIT Repos

• Setting-Up-the-Server

Github

Create pull requests

• https://opensource.com/article/19/7/create-pull-request-github

Signing commits using GPG

• https://gist.github.com/ankurk91/c4f0e23d76ef868b139f3c28bde057fc

How do I update a GitHub forked repository?

• Source

Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

Fetch all the branches of that remote into remote-tracking branches

git fetch upstream

Make sure that you're on your master branch:

git checkout master

Rewrite your master branch so that any commits of yours that aren't already in upstream/master are replayed on top of that other branch:

git rebase upstream/master

If you don't want to rewrite the history of your master branch, (for example because other people may have cloned it) then you should replace the last command with git merge upstream/master. However, for making further pull requests that are as clean as possible, it's probably better to rebase.

If you've rebased your branch onto upstream/master you may need to force the push in order to push it to your own forked repository on GitHub. You'd do that with:

git push -f origin master

tweaks

how to change commit message

GitHub's instructions for doing this:

1. On the command line, navigate to the repository that contains the commit you want to amend.
2. Type git commit --amend and press Enter.
3. In your text editor, edit the commit message and save the commit.
4. Use the git push --force example-branch command to force push over the old commit.