|
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... | |
| | | | |
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... | |
| | | | |
kokada.dev
|
|
| | | |||