Closed jmini closed 2 months ago
It seems that GitLab has introduced a new status approvals_syncing, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150946
approvals_syncing
Currently when ucascade gets this status, instead of re-trying later it assign the MR responsible and requires a manual handling of the MR.
Probably ucascade can be improved and deal with this state. Maybe the code can be changed to be more robust and re-try in all "unknown" cases.
It seems that GitLab has introduced a new status
approvals_syncing, see https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150946Currently when ucascade gets this status, instead of re-trying later it assign the MR responsible and requires a manual handling of the MR.
Probably ucascade can be improved and deal with this state. Maybe the code can be changed to be more robust and re-try in all "unknown" cases.