Skip to content

hot-fix: look up only push runs for a PR's base - #1249

Merged
ovflowd merged 1 commit into
mainfrom
meta/compare-push-runs
Nov 6, 2026
Merged

ovflowd merged 1 commit into
mainfrom
meta/compare-push-runs

Conversation

@ovflowd

@ovflowd ovflowd commented Nov 6, 2026

Copy link
Copy Markdown
Member

Description

This PR is a follow-up to #1248, which didn't quite fix it, my bad. prepare looked up the latest run of generate.yml for the PR's base commit, of any event. For a PR stacked on another PR's branch, that finds the lower PR's pull_request run, which never uploads the commit artifact, so the download still failed. It now looks up only push runs (-e push): a stacked base finds none and skips the comparison as #1248 intended, while a base on main finds the same run as before.

Validation

Checked the lookup against the real runs. For #1238's base (perf/stream-worker), it found #1237's pull_request run before and finds nothing with -e push. For main's head, both find the same push run. zizmor reports nothing new, and the format check passes.

Related Issues

Refs: #1248

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run node --run test and all tests passed.
  • I have check code formatting with node --run format:check & node --run lint.
  • I've covered new added functionality with unit tests if necessary.

Only push runs of generate.yml upload the `commit` artifact. A PR
stacked on another PR's branch can find that PR's pull_request run for
its base commit, so prepare tried to download an artifact that run
never made, and failed. With -e push such a base finds no run, and
prepare takes the path without a comparison that #1248 added.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
api-docs-tooling Ready Ready Preview Nov 6, 2026 7:33pm UTC

Request Review

@codecov

codecov Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.13%. Comparing base (9d288fe) to head (348b3e8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1249   +/-   ##
=======================================
  Coverage   94.13%   94.13%           
=======================================
  Files         291      291           
  Lines       28900    28900           
  Branches     2932     2932           
=======================================
  Hits        27206    27206           
  Misses       1672     1672           
  Partials       22       22           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅

View logs ↗
No Preview URL. Enable ↗ 348b3e8 2026-11-06T19:33:58.448Z View logs ↗

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

api-links Generator

Performance estimate (single CI run)

  • Generation time: 5.1% slower (980.00 ms → 1.03 s)
  • Peak memory: 0.2% lower (276.03 MB → 275.57 MB)

json Generator

Performance estimate (single CI run)

  • Generation time: 22.5% faster (6.80 s → 5.27 s)
  • Peak memory: 6.7% higher (899.29 MB → 959.45 MB)

legacy-html Generator

Performance estimate (single CI run)

  • Generation time: 57.6% slower (9.22 s → 14.53 s)
  • Peak memory: 1.3% lower (1.43 GB → 1.41 GB)

legacy-json Generator

Performance estimate (single CI run)

  • Generation time: 0.9% slower (8.69 s → 8.77 s)
  • Peak memory: 1.0% lower (961.79 MB → 951.99 MB)

llms-txt Generator

Performance estimate (single CI run)

  • Generation time: 2.0% faster (8.00 s → 7.84 s)
  • Peak memory: 6.5% lower (896.54 MB → 838.29 MB)

orama-db Generator

Performance estimate (single CI run)

  • Generation time: 8.1% faster (8.85 s → 8.13 s)
  • Peak memory: 10.2% higher (984.24 MB → 1.06 GB)

web Generator

Performance estimate (single CI run)

  • Generation time: 2.4% faster (22.93 s → 22.38 s)
  • Peak memory: 2.3% lower (1.50 GB → 1.47 GB)

@ovflowd ovflowd added the fast track This PR can land before the typical review time, with a :+1: from collaborators label Nov 6, 2026
@ovflowd

ovflowd commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Apologies team (cc @nodejs/doc-kit) hot fix of my previous one... Don't have @act installed locally so wasn't able to confirm it fixed 100% the workflow T.T

@ovflowd
ovflowd merged commit 61fa0b9 into main Nov 6, 2026
25 of 26 checks passed
@ovflowd
ovflowd deleted the meta/compare-push-runs branch November 6, 2026 19:42
@ovflowd ovflowd changed the title meta: look up only push runs for a PR's base hot-fix: look up only push runs for a PR's base Nov 6, 2026

This branch was successfully deployed

1 active deployment
Preview – api-docs-tooling — 348b3e89 Deployed Nov 6, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fast track This PR can land before the typical review time, with a :+1: from collaborators

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant