bard86

Restore intentionally deleted commits in Git (remote)

Situation

1. You own a Git repository server and the developers do not have access to it (i.e. they can only read & write to the repo, but not gc it).
2. You had a developer that wrote a project for you.
3. He got angry for whatever reason and deleted all branches from the remote repo. He also push -fed the master branch leaving only one silly commit there.
4. He escaped from the country leaving you without any code at all (at least this is what he believe in).
5. You have never cloned the repo to other machine. There were only two copies of it: the developer's one and the server's one.

bard86

UPDATE: A better way! (August 2015)

As pointed out by @johntyree in the comments, using git reflog is easier and more reliable. Thanks for the suggestion!

 $ git reflog
1ed7510 HEAD@{1}: checkout: moving from develop to 1ed7510
3970d09 HEAD@{2}: checkout: moving from b-fix-build to develop
1ed7510 HEAD@{3}: commit: got everything working the way I want
70b3696 HEAD@{4}: commit: upgrade rails, do some refactoring

bard86

GIT_SSH_COMMAND='ssh -i private_key_file' git clone user@host:repo.git

bard86

docker network create \
       --driver bridge \
       --subnet=192.168.16.0/20 \
       atlassianNetwork
  
docker volume create --name bambooVolume

docker run -d -p 8085:8085 -v bambooVolume:/var/atlassian/application-data/bamboo \
  --name bamboo \
  --network atlassianNetwork \

bard86

export PS1="\u@\h [\W]: \[$(tput sgr0)\]"

bard86

#!/bin/bash
set -e

sudo hostname MacBook.local
scutil --set HostName MacBook.local

bard86

#!/bin/bash

ssh-keygen -t rsa -C "@gmail.com" -f $HOME/.ssh/id_rsa_file

bard86

export PATH="/usr/local/opt/openjdk/bin:$PATH"

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

export PATH="$HOME/.jenv/bin:$PATH"
  eval "$(jenv init -)"

bard86

Demo:

Spoiler warning

Spoiler text. Note that it's important to have a space after the summary tag. You should be able to write any markdown you want inside the <details> tag... just make sure you close <details> afterward.

console.log("I'm a code block!");

bard86

#!/bin/bash
set -e

defaults write com.apple.Finder AppleShowAllFiles true