Explore >> Select a destination
|
You are here 
|
nvie.com | ||
| | | | |
www.elidedbranches.com
|
|
| | | | | Technology, startups, programming, technical management and software architecture | |
| | | | |
techblog.izotope.com
|
|
| | | | | Nick Donaldson Version control is an indispensable tool in modern software development, and Git is one of the most popular and widely used version control systems available today. However, despite its pervasiveness, many development teams do not use Git to its full potential, often due to a lack of a well constructed and adhered-to Git... | |
| | | | |
raphael.medaer.me
|
|
| | | | | A decade ago, Vincent Driessen wrote a post named "A successful Git branching model". In his post he presents a development model using many Git branches (master, develop, ...) well known as the Git flow. Even if I'm not doing professional development for ten years, I got the opportunity to experiment Git flows in many development teams. As explained by his "Note of reflection (March 5, 2020)", you should not treat this flow as a dogma or panacea. While the flow I will describe in the following lines is ... | |
| | | | |
pradyunsg.me
|
|
| | | I have a (somewhat unnecessarily) custom setup for managing my dotfiles and I made a nice improvement to it today. How it works The dotfiles are managed by a Python script. In broad strokes, the script will: read a TOML file locate the configured paths create symlinks, based on custom marker text in the filenames, for files in subdirectories under the configured paths1 If there's a conflict (i.e. two configured paths provide the same symlink target location), the TOML file contains the resolution for it (i. | ||
