Explore >> Select a destination
|
You are here 
|
blog.waleedkhan.name | ||
| | | | |
qsantos.fr
|
|
| | | | | tl;dr: I do not like merging the main branch into feature branches, and I do not like squashing MR/PRs git commit git has emerged as the obvious choice for SCCS (Source Code Control System). The consensus is that it is unambiguously better than the previous standard, SVN. There is some debate as to what is [...] | |
| | | | |
blog.kulman.sk
|
|
| | | | | When working on iOS applications, I often find myself in situations where I need to develop a new feature while simultaneously fixing a bug. This can be challenging to manage, especially when the changes for the feature and the bug fix overlap. Developers have different approaches to handle this: Stashing changes Creating temporary commits Cloning the repository twice While these methods work, they are not ideal. Recently, I discovered a better solution. | |
| | | | |
blog.bloomca.me
|
|
| | | | | The blog of Seva Zaikov | |
| | | | |
felipec.wordpress.com
|
|
| | | Probably one of most powerful and under-utilized concepts of git is the upstream tracking branch, and to be honest it probably was too difficult to use properly in the past, but not so much any more. Here I'll try to explain what it is, and how you can take the most advantage out of it.... | ||
