FYI in an emergency you can SSH to your server and edit files and the DB directly.

Where is your god now, proponents of immutable filesystems?!

I love when people do that because they always say "I will push the fix to git later". They never do and when we deploy a version from git things break. Good times.

I started packing things into docker containers because of that. Makes it a bit more of a hassle to change things in production.

Depends on the org, the big ones I've worked for regular Devs even seniors don't have anything like the level of access to be able to pull a stunt like that.

At the largest place I did have prod creds for everything because sometimes they are necessary and I had the seniority (sometimes you do need them in a "oh crap" scenario).

They where all setup on a second account in my work Mac which had a danger will Robinson wallpaper because I know myself, far far too easy to mentally fat finger when you have two sets of creds.

It's easier, when the deployed instance on the server is also a Git repo, so you can commit the changes there and pull.

FYI in an emergency, you can buy a plane ticket and send someone to access the server directly.

I actually had the privilege of being sent to the server.

Had a coworker have to drive across the country once to hit a power button (many years ago).

Because my suggestion they have a spare ADSL connection for out of channel stuff was an unnecessary expense... Til he broke the firewall knocked a bunch of folks offline across a huge physical site and locked himself out of everything.

The spare line got fitted the next month.

I'm actually getting "ERROR: no healthy upstream" on `git pull`.

They done borked it good.

If your remote is set to a [email protected] remote, it won't work. They're just pointing out that you could use git to set origin/your remote to a different ssh capable server, and push/pull through that.