Also Trump literally illegally kidnapped a head of state to the U.S. And we’re supposed to pretend the first thing they did was not simply… Move the murderer somewhere out of state where they couldn’t reach him even if they tried (which they won’t because no blue state has the balls to meaningfully stand up to Trump)?

I mean, realistically that guy could twerk in front of the Minnesota Capitol with some ICE buddies to back him up and giant sign saying “I did it” and Minnesota still wouldn’t do shit.

“State’s rights” are exactly like the “2A rights”. They only serve conservatives, whom the law protects but does not bind.

This is not just me being salty BTW. I am trying to get across the point to anyone reading this that if your plan to bring back U.S. Democracy relies on the Constitution playing in your favor, you’ve already lost.

Ideally you’d use the docker executor with a dind service instead of docker commands in the shell. You’ll have better isolation (e.g. no conflicts from open port forwards) and better forward-compatibility (the pipeline won’t break every time a major upgrade is applied to the runner because the docker - especially compose - CLI is unstable).

For gitlab this is only correct with a shell executor which is to be avoided in the general case in favor of a docker or k8s executor for isolation&repeatability.

Those you can actually run locally with gitlab-runner, but then you won’t have all your gitlab instance’s CI variables so it’s a PITA if you need a CI token which you probably do if you actually make decent use of gitlab’s features.

In most cases I just end up committing my changes to avoid the headache. :!git commit --amend --no-edit && git push -f goes pretty dang fast and 60 % of the time third time’s the charm.