Neat little summary on the mechanisms to ignore files in Git.
Looks like some governments noticed that they can move away from GitHub and are testing the waters. Good idea!
This is indeed time to move away from GitHub if you're still there. There are many viable alternatives.
Good first half of the post, there's indeed more paths out of GitHub than jumping from a centralised system to another one (even though Codeberg and Forgejo are much saner from a governance standpoint). We'll see what the future brings.
A single CLI tool for any Git forge? This sounds appealing.
Nice quality of life improvements for the history rewrites. That said, I'm particularly looking forward to the changes in hooks handling, it's always been a pain to deal with in teams, moving them to config should help.
Nice little commands to use to discover quickly the state of a code base... Or rather of its team.
Git bisect won't help much for flaky tests... but maybe this bayesian approach can.
We're not helped much by our tools here... Clearly provenance needs to be double checked.
A reminder that this is an easy migration. Can also be towards you own instance of Forgejo of course.
Interesting trick in Got, using SSH certificates to prove the origin on commits. This feels a bit rough though, tooling has room for improvement.
This looks tempting. I guess I'll try this one instead of pre-commit when I get the chance.
Nice little git trick. We can all thank the CIA I guess?
A good reminder that Git doesn't force you to use a web application to collaborate on code.
This kind of migration is apparently easier than it sounds.
Very good move on their part. It's time more people do so. Beside, Forgejo (powering Codeberg) looks very interesting. I plan to play with it more next year.
Nice tour of LazyGit. I keep hearing good things about it, I should really try it.
A good reminder that you don't always need a full blown forge.
Git pre-commit hooks indeed bring nice benefits. Like everything else they're not a panacea though.
An old series of posts which highlights quite well why GitFlow can be a problem and that you likely want something simpler. Since I still find GitFlow often recommended as a knee-jerk reaction, this is a good article to have in hand.