fix: treat pending Gitea CI as acceptable on synced main

Normal Portal releases should not block when commit status stays pending after the candidate is already pushed to origin/main. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-27 22:36:40 +08:00
parent 82b74d71ad
commit a95681ea3a
3 changed files with 17 additions and 6 deletions
@@ -20,18 +20,22 @@ test('release CI accepts explicit success and rejects explicit failure', () => {
  );
 });

-test('release CI accepts missing status when candidate equals origin/main', () => {
+test('release CI accepts missing or pending status when candidate equals origin/main', () => {
  const sha = 'c7718c683b216f08865e04edc67f4217f6abc3c1';
  assert.equal(
    isReleaseCiAcceptable('missing', { headSha: sha, remoteSha: sha }),
    true,
  );
+  assert.equal(
+    isReleaseCiAcceptable('pending', { headSha: sha, remoteSha: sha }),
+    true,
+  );
  assert.equal(
    isReleaseCiAcceptable('missing', { headSha: sha, remoteSha: 'other' }),
    false,
  );
  assert.equal(
-    isReleaseCiAcceptable('pending', { headSha: sha, remoteSha: sha }),
+    isReleaseCiAcceptable('pending', { headSha: sha, remoteSha: 'other' }),
    false,
  );
 });