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?
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:
… just to name a few
bin/ for common tasks
CD == Continuous Delivery, which can also mean publishing a new “release candidate” artifact. Maybe there is a more stringent QA system downstream, such as QA teams after a car gets a firmware update to that release candidate.
This happens on the consumer side too, with risk averse customers, even if they adopt a continuous delivery paradigm upstream. It’s also a common argument against a rapid release model, but is often dismantled when appropriate, automated safeguards are put in place. Not always possible to automate everything, due to regulations, but automating the bulk of the tests are in everyone’s best interests.
How are those tests triggered? On developer machines? Not very reliable that a human will remember to execute them, even if it was possible to run them all from a workstation. That’s why there’s a bastion host or, hopefully, set of hosts to run those tests and builds. That’s the CI/CD system. That’s the value.