You know the basics - branches, merges, pull requests. Now it's time to clean up after yourself. Rebasing, squashing, stashing, and the safety net that means you can't actually break anything.
Time to get practical. Set up Git, version control your network configs, learn branching and merging the hard way (by breaking things), and open your first pull request on GitHub.
As network engineers, we've been solving version control problems badly for years, dated backup files, manual comparisons, config files named final_v2_WORKING.txt. Git exists because developers hit this wall decades ago. It's time we caught up.
Intro Short blog post, as many of you, will just want to fiddle with the playbook(s) itself. GitHub repo
