N/A

In case I didn't explain correctly I'll put this example:

**I have a deploy X running perfectly. I make a commit, which creates a deploy Y which crashes because my code sucks. In that case, my app would just go offline until I rollback or I make another commit. **

Is there a way to avoid this, by rollbacking to the previous deploy automatically in case of a crashed deployment?

No, this is not possible. If your goal here is to maintain a stable environment while also developing and potentially pushing unstable code, you'd want to have two environments separated by Github branches

alr tysm

!s