Explore >> Select a destination
|
You are here 
|
jamesmead.org | ||
| | | | |
lostfocus.de
|
|
| | | | | How do you nice people reading my blog handle your Github account(s)? I've had my "main" account @lostfocus for ages and used it for pretty much everything I needed to do on Github. Now with my current employer our accounts are put into the SSO system, so I created a second account which went through ... | |
| | | | |
blog.bdw.li
|
|
| | | | | Using different machines to work on some git files can result in missing signign keys and some headache. | |
| | | | |
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... | |
| | | | |
danielpecos.com
|
|
| | | In a previous post, we have seen what Git is and its main characteristics. Now, we'll go more into detail about its functionality and we'll see what a usual day working with Git looks like. But before, some initial concepts: Repository: A working tree of files and directories which can be versioned, keeping track of every single modification made over the working tree, been able to move forward and backward in its history. | ||
