Explore >> Select a destination
|
You are here 
|
cassidoo.co | ||
| | | | |
alex.pearwin.com
|
|
| | | | | A shortcut to launch a ROOT TBrowser from the terminal. | |
| | | | |
purefun.dev
|
|
| | | | | If you install a new machine and forget to set your email and commiter name, then your Git history will be a tad ugly, with your machine name involved instead of a real email. So how do you set the default? Like this: git config --global user.name "Alice E" git config --global user.email "alice@example.org" Override per repo Ideally, do it before you start committing things. But what if you want different committer names and emails depending on the context? | |
| | | | |
blog.kulman.sk
|
|
| | | | | I use the same machines to work on both personal and work projects. I usually have to use a different Git identity for the work projects than for my personal projects. Previously I had my personal Git identity set globally and then used local Git configs to override it in work projects. This worked just fine but it was too much work. There is a better solution. Git config allows you to use, or better to say include, another Git config for a specific directory and all its subdirectories. I have all my pro... | |
| | | | |
ewintr.nl
|
|
| | | [AI summary] This article explains how to set up a simple CI/CD pipeline using bash scripts and git hooks to automate deployment processes, including deploying to production and staging environments with user permissions management. | ||
