slashdeploy/locked commit status

[turadg]

When prod deploy is locked sometimes lots of commits pile up in master that don't get deployed until the unlock, which weighs the unlock with unnecessary risk.

Would be great to have a Github status check that fails if production is locked.

[ejholmes]

Do you think #60 will solve this? When this happens, you'll get a DM from @slashdeploy saying:

Hey @turadg. I was going to deploy xxx to production for you, but production is locked.

[turadg]

That will be useful for letting people know their commits to master won't deploy. What I'm after here is to prevent committing to master when deploy is locked. (So that commits don't pile up and potentially introduce new problems when the unlock and deploy finally happens.)

[ejholmes]

Ahhh, I see what you're saying. That's a really good idea, and I think would be relatively straightforward to implement.

[turadg]

Credit goes to @jerrysu. Ran into him on my walk into work the other day and his new stack has this feature. He said they have almost a dozen status checks. (e.g. linting is checked separately from unit tests)