Gitlab won't allow reuse of a public ssh key for multiple accounts. To get around this you need to create a second ssh key for the second account.
Create or modify your ~/.ssh/config file:
# normal
Host gitlab.com-work_username
HostName gitlab.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa
| # to get in a terminal: curl -X GET http://is.gd/installzsh_sh > installzsh.sh | |
| TARGET_USER=$1 | |
| echo "Installing zsh..." | |
| sudo apt-get install git curl zsh -y > /dev/null; | |
| echo "Installing oh-my-zsh" | |
| if [ "$TARGET_USER" != "" ]; then | |
| echo "Installing oh-my-zsh for user $TARGET_USER"; | |
| export RUNZSH=no |
| #!/bin/bash | |
| # settings | |
| # Login information of freenom.com | |
| freenom_email="main@address" | |
| freenom_passwd="pswd" | |
| # Open DNS management page in your browser. | |
| # URL vs settings: | |
| # https://my.freenom.com/clientarea.php?managedns={freenom_domain_name}&domainid={freenom_domain_id} | |
| freenom_domain_name="domain.name" |
As configured in my dotfiles.
start new:
tmux
start new with session name:
| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork [email protected] |