This kind of misses the point, though. I would say a much better rule is whatever runs in your workflows should also be entirely reproducible locally.

Even if you can ssh into the remote environment that does not cover things like authentication and authorization, you don't just git a GITHUB_TOKEN with the same permissions.

▲

Storment33 2 hours ago | parent [-]

Exactly, you should be able to do everything locally! All this needing to SSH into runners or needing self-hosted runners or needing act to emulate GitHub Actions is really a failure of the developer experience.

▲

whynotmaybe an hour ago | parent [-]

A lot of stuff can be handled by developer themselves, but usually some steps are voluntarily blocked, like publishing to Google Play/App store.

You don't want anyone to be able to publish public facing app from their version of the code that might not be committed.

Some of us remember an era where deployment was copy-paste from the local /bin folder to the /bin folder on production server.

	▲	Storment33 an hour ago \| parent [-]
		While I get some stuff you can't test locally, like 90%+ of complaints I see are for builds/tests. Which is really a failure of the engineers for not having a local feedback loop. I am of the opinion you should be able to deploy from your machine, just you do not have the permissions to normally. So that if CI ever goes down and you need to push an emergency fix or something you can break glass if needed.