Mostly yes, but they’re in general oversimplified (for obvious reasons)

But it’s more about offensive cyber security than necessarily the Linux part. The Linux part is just file system navigation and not much more, the rest is the “hacking” part, and that’s what I’m talking about

Disclaimer: I did not complete it, but I got pretty far, and I worked in the cyber security area.

I would however say it’s not a good place if you want to learn as that’s not really the game’s focus. There are better resources out there like overthewire and linuxjourney for that

Wait, you’re not AI too?

Shared branches should always only move forward. Most Git-* systems support stuff like protected branches.

I personally like tidying up your own feature branch with rebasing and then merging it into main (preferably using only FF merges). However this is not scalable for some larger projects, and for example monorepos also make this hard to accomplish. In those cases the solution ends up being squash+merge.

The extra information about the squashed commits is usually persisted to these systems (GitHub PRs, GitLab MRs, etc) so you don’t really lose much, I guess. Although I do prefer keeping it all in plain git.

Hasn’t been the case anymore for quite some time, even though I think it has quite generous sudo rules. But yes, it’s not meant to be your main OS but instead more like a toolbox you use in liveboot/VM/etc.