3.0 KiB
| title | tags | ||
|---|---|---|---|
| git |
|
Starting
New Machines
git config --global user.email "$YOUR_EMAIL"
git config --global user.name "$YOUR_NAME"
New Git
Start a git in directory $DIR:
mkdir $DIR && cd $DIR
git init
Make a file explaining what the project does:
vim README.md
Add this to the git:
git add README.md
Then make the initial commit, explaining the change you just made:
git commit
Working
Once you make a change to some file, add it and make a commit explaining it.
git add $FILE
git commit -m"change $FILE"
Check your history:
git log
Remotes
If you want to keep a copy on a public site such as Gitlab, so others can see it, then go there and create a blank project (no readme, nothing).
Give it the same name as the $DIR directory, above.
Add this as a remote:
REMOTE=gitlab
git remote add $REMOTE https://gitlab.com/$USERNAME/$DIR
Tell git you're pushing the branch "master" to the remote repo "origin":
git push -u master origin
If someone makes a change on the remote, pull it down with:
git pull
Branches
A branch is a full copy of the project to test additional ideas. You can make a new branch called 'featurez' like this:
git branch $FEATURE_BRANCH
Have a look at all your branches:
git branch
Switch to your new branch:
git checkout $FEATURE_BRANCH
And if your changes are rubbish, checkout the "master" branch again, then delete "featurez":
git branch -D $FEATURE_BRANCH
Or if it's a good branch, push it to the remote:
remote=origin
git push $remote $FEATURE_BRANCH
Merging
Once you like the feature, merge it into the main branch. Switch to master then merge it:
git merge $FEATURE_BRANCH
And delete the branch, as you've already merged it:
git branch -d $FEATURE_BRANCH
Subtree
Pulling another git repo into a subtree
git subtree add -P config git@gitlab.com:bindrpg/config.git master
Tricks
Delete All History
git checkout --orphan temp
git add -A
git commit -am "release the commits!"
git branch -D master
git branch -m master
git push -f origin master
Gitlab requires more changes, such as going to settings > repository and switching the main branch, then stripping protection.
Clean up Bloated Repo
git fsck --full
git gc --prune=now --aggressive
git repack
Find Binary Blobs
git rev-list --objects --all \
| git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' \
| sed -n 's/^blob //p' \
| sort --numeric-sort --key=2 \
| cut -c 1-12,41- \
| $(command -v gnumfmt || echo numfmt) --field=2 --to=iec-i --suffix=B --padding=7 --round=nearest
More
For big binary files (like images), see git large-file-storage