According to documentation:
> By default, check suites are automatically created when you create a check run.
But it seems sometimes when there are multiple check runs are created at the same time for the same SHA there might be a race condition that creates two Check Suites (link to a corresponding check run):
On the another hand, when a CheckSuiteEvent is requested via a webhook event (which in our case triggers a build which creates thouse check runs), check_suite in a payload of the event already contains Check Suite’s id that is requested. But an API enpoint to create a Check Run doesn’t allow to provide a check_suite_id which can help with fixing the race condition.
Is my understading of why there are two Check Suites correct? Can I do something beside executing calls to create check runs for the same SHA sequential rather then parallel.