We have our own really solid deployment method here but one issue with it is that mostly, the apps get deployed but if the integration between abra and the app is broken, we don't see a failure. So, I would say that we should use abra to deploy the apps with stack-ssh-deploy. That can either configurable or we just go all in on dogfooding our own tools and re-write logic to use abra. That may just even turn out to be simpler.
We have our own really solid deployment method here but one issue with it is that mostly, the apps get deployed but if the integration between abra and the app is broken, we don't see a failure. So, I would say that we should use abra to deploy the apps with stack-ssh-deploy. That can either configurable or we just go all in on dogfooding our own tools and re-write logic to use abra. That may just even turn out to be simpler.
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.
We have our own really solid deployment method here but one issue with it is that mostly, the apps get deployed but if the integration between abra and the app is broken, we don't see a failure. So, I would say that we should use abra to deploy the apps with stack-ssh-deploy. That can either configurable or we just go all in on dogfooding our own tools and re-write logic to use abra. That may just even turn out to be simpler.
Can continue on https://git.coopcloud.tech/coop-cloud/organising/issues.