|
You are here |
blog.differentpla.net | ||
| | | | |
markentier.tech
|
|
| | | | | I work across 2 computers and 3 OS, all with nearly same development setup. For work I need some special care for my git... | markentier.tech | |
| | | | |
themythicalengineer.com
|
|
| | | | | The Big Problem Imagine you have two GitHub accounts: one for personal use and one for work. You might be working on personal projects from your work laptop, but switching between these projects often requires manually updating your GitHub configuration: | |
| | | | |
willhaley.com
|
|
| | | | | This article outlines a process for loading a custom git configuration when in a specific directory tree. This sets up a sort of local git configuration per-directory without needing to alter the global .gitconfig file or any other global git or ssh configurations. See here an example .envrc file. This file would be used by direnv to set per-directory env variables with the direnv shell helper. PATH=$PATH:$(pwd)/bin export GIT_AUTHOR_EMAIL="Email to use for this organization" export GIT_AUTHOR_NAME="Name to use for this organization" export GIT_COMMITTER_EMAIL="Email to use for this organization" export GIT_COMMITTER_NAME="Name to use for this organization" export GIT_SSH="my-special-ssh-command-for-this-organization.sh" Setting GIT_SSH allows for customizing the ssh command and identity used for this directory. | |
| | | | |
blog.gnoack.org
|
|
| | | |||