Explore >> Select a destination
|
You are here 
|
memo.mx | ||
| | | | |
ianduffy.ie
|
|
| | | | | Learn how to seamlessly switch between work and personal GitHub accounts using SSH, GPG, and SSH agent configurations. This guide walks you through setting up 1Password for secure key management, configuring Git for different identities, and automating the process to enhance your development workflow. | |
| | | | |
vadosware.io
|
|
| | | | | Yet another article on the internet about how to reasonably manage multiple git personas | |
| | | | |
www.micah.soy
|
|
| | | | | Working on many projects across multiple identities can be difficult to manage. This is a procedure for leveraging git aliases to set an identity at the project level. | |
| | | | |
zzamboni.org
|
|
| | | via http://www.codinginahurry.com/2011/02/05/three-levels-of-git-config/ Very nice explanation, viacoding in a hurry There are 3 levels of git config; project, global and system. project: Project configs are only available for the current project and stored in .git/config in the project's directory. global: Global configs are available for all projects for the current user and stored in ~/.gitconfig. system: System configs are available for all the users/projects and stored in /etc/gitconfig. Create a pr... | ||
