Explore >> Select a destination
|
You are here 
|
blog.kulman.sk | ||
| | | | |
blog.bdw.li
|
|
| | | | | Using different machines to work on some git files can result in missing signign keys and some headache. | |
| | | | |
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 customizin... | |
| | | | |
jinyuz.dev
|
|
| | | | | Suppose that you have a full time job at Amazon, and you want to separate your git commit emails from Amazon and your personal projects. Setting up ~/.gitconfig $ touch ~/.gitconfig For our personal projects, we will use the ~/.gitconfig file with the following content: [user] name = James Banned email = james.banned@gmail.com [includeIf "gitdir:~/Work/"] path = ~/.gitconfig.work The includeIf basically means that include this config if I'm inside the ~/Work/ directory. | |
| | | | |
vadosware.io
|
|
| | | Yet another article on the internet about how to reasonably manage multiple git personas | ||
