Haven't looked into this since cutting the issue, but the flow for file modifications on a server is suspect anyways
Currently we push the files, and then hold the restart behind a few safety gates + a queuing system
This isn't a good idea though. We should push the files after clearing the gate, but before the restart. We should not be making modifications to a production instance that hasn't been through the empty server checks and other associated safety gates
Haven't looked into this since cutting the issue, but the flow for file modifications on a server is suspect anyways
Currently we push the files, and then hold the restart behind a few safety gates + a queuing system
This isn't a good idea though. We should push the files after clearing the gate, but before the restart. We should not be making modifications to a production instance that hasn't been through the empty server checks and other associated safety gates
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
i think.. needs more investigating, but it's possible we just need to move file modification to right after empty server verification
Haven't looked into this since cutting the issue, but the flow for file modifications on a server is suspect anyways
Currently we push the files, and then hold the restart behind a few safety gates + a queuing system
This isn't a good idea though. We should push the files after clearing the gate, but before the restart. We should not be making modifications to a production instance that hasn't been through the empty server checks and other associated safety gates