Explore >> Select a destination
|
You are here 
|
www.maxpou.fr | ||
| | | | |
tannerdolby.com
|
|
| | | | | To begin contributing to open-source software, you might want to become familiar with Git. Understanding the workflow of creating your own local copy of a repository and keeping it up to date with the upstream repository is integral to start contributing in public projects. | |
| | | | |
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. | |
| | | | |
felixrieseberg.com
|
|
| | | | | Git worktrees: Work in multiple branches at the same time. Quit reinstalling dependencies when you checkout different branches. | |
| | | | |
ryanharter.com
|
|
| | | This is the second post in my Start to Finish series. You can check out my first post introducing the series and my tools here. What is SCM? SCM, or source code management, is a system that helps developers manage the source code for their projects. They have been around forever, things like CVS, Subversion (SVN) and now Git are the popular ones. SCMs allow you to version your source code, which is why they are also called Version Control Systems. | ||
