Hey, I run my own CI/CD environment instead of using GitHub. When I push a commit and a workflow starts, I actively call the GitHub Status API (is that what it’s called?) to report the current CI status (pending, success, error).

Between the push and the start of the workflow—and then the update of the status—there is always a short delay (a few seconds), which is of course a bit longer than GitHub’s own status, which is set almost immediately.

Disclaimer: “Wait for CI” is, of course, enabled.

Unfortunately, this leads to the problem that the services deploy immediately without waiting for the CI results (e.g. running unit tests). I probably don’t need to go into detail about why this is problematic. That’s why it would be great if it were possible to configure a short waiting period or something similar 🙂

I assume that only relatively few people are affected by this little issue, so one might want to consider whether it’s worth taking into account . In my opinion, however, it would lead to a slightly smoother deployment DX (and who wouldn’t want that?).