That’s hilarious because for automated access to the API, without tying to a single specific user account (for attrition purposes), my company was advised by Microsoft Support to create a service account for that API access. The process was the exact same as any other user account because… it WAS like any other user account.

Killer feature of gitlab that I have yet to see replicated is automatic repo creation on git push. This makes GitLab my go-to for this role.

Like what?

• OCI registry? GitLab.
• pull request model? Every one of the competing services
• CI/CD system based on YAML definitions? Most every competitor.
• static site hosting? Most competitors
• protected branches? Most competitors

I’m not saying there isn’t vendor lock-in, but I am saying it likely isn’t the features of GitHub that are limiting that. Third party integrations will follow wherever the foot traffic goes.

Incoming job board spam:

• weworkremotely.com
• remoteok.com
• dailyremote.com
• flexjobs.com
• remote.co
• remotive.com
• virtualvocations.com

… just to name a few

• direnv
• nixpkgs (with flakes enabled)
• committed flake.nix and flake.lock
• Makefile or several shell scripts in bin/ for common tasks

(explainer)