Browse Source
The current CI setup sets the manifest DNM label in a workflow and checks it in a different workflow. The one performing the check is configured to rerun on label changes but it's been reported few times that the rerun logic does not seem to always run effectively and there's been cases where the manifest has been fixed but the label has not been removed by the automation, resulting in a stale PR. Since the manifest has its own dedicated label, fix this race condition by checking for that label specifically in the manifest workflow rather than in a separate one, this means that the check is always performed after the script that sets the label. It also means that on manifest changes the manifest step itself will fail rather than the PR metadata check one. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>pull/88808/head
2 changed files with 7 additions and 1 deletions
Loading…
Reference in new issue