CLOUDY MUSINGS

At some point you look across your repos and realize you've got some sort of split personality problem. Half your projects are on main, the other half are still on master, and every time you touch a pipeline, clone a repo, or write documentation, you have to stop and remember which one you're dealing with. You know it's not broken, it's just inconsistent enough to be a persistent low-grade annoyance. I recently went through this myself and thought about adding this to my blog

Why You Should License Your GitHub Repository When you publish code on GitHub without a license, you automatically retain full copyright. That means others can read your code, but they cannot legally copy it, modify it, or redistribute it. In short: Public does not automatically mean open source. No license means no permission for reuse. GitHub is explicit about this. For a repository to be considered open source, it must include a license that grants others the right to use,

So there I was, ready to pull down a GitHub repo and get to work finishing a recent blog. I typed in the familiar command: git clone ...

If you've paid attention this entire time, there were 3 previous posts: Source Control Ninja Level - Pt. 1 Definitions Source Control...

So if you're like me, you've been having more and more conversations that are a bit of a stretch from your infrastructure roots....