ci(backport): include full commit SHA in no-backport comment#2057
Merged
Conversation
GitHub Actions doesn't currently support prefilling workflow_dispatch inputs via URL query params (community/community#51159), so the "override via workflow_dispatch with this commit SHA" instruction in the no-backport comment required the reader to go look up the SHA themselves. Paste the full 40-char SHA into the comment in a fenced code block so it's one click to copy into the "Commit SHA" input on the workflow run page.
Contributor
|
Contributor
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 sequential data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 10 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 25 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro workflow with 50 concurrent data payload steps (10KB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro stream pipeline with 5 transform steps (1MB)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro 10 parallel streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro fan-out fan-in 10 streams (1MB each)💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
❌ Some benchmark jobs failed:
Check the workflow run for details. |
Contributor
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests💻 Local Development (1 failed)express-stable (1 failed):
📦 Local Production (1 failed)nextjs-turbopack-canary (1 failed):
🐘 Local Postgres (1 failed)nextjs-webpack-canary (1 failed):
Details by Category✅ ▲ Vercel Production
❌ 💻 Local Development
❌ 📦 Local Production
❌ 🐘 Local Postgres
✅ 🪟 Windows
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
karthikscale3
approved these changes
May 21, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR improves the “no backport” PR comment emitted by the Backport to stable GitHub Actions workflow so that it includes the full commit SHA needed to manually override the AI decision via workflow_dispatch.
Changes:
- Include both a short (7-char) SHA for readability and the full 40-char SHA for copy/paste in the no-backport PR comment.
- Add an inline code comment explaining why the workflow cannot link to a prefilled
workflow_dispatchform (GitHub Actions limitation).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
|
No backport to This change only modifies To override, re-run the Backport to stable workflow manually via |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The no-backport comment posted by the backport workflow ends with:
…but "this commit SHA" was never actually included in the comment, so anyone wanting to override the AI's decision had to go look it up.
GitHub Actions does not currently support prefilling
workflow_dispatchinputs via URL query params (community/community#51159, open since 2023), so we can't link the user directly to a prefilled form. Instead, this PR pastes the full 40-char SHA into the comment inside a fenced code block, making it a one-click copy into the "Commit SHA" input on the workflow run page.Also includes a code comment explaining why we're not just linking to a prefilled dispatch form, so the next person who has the same idea finds the answer immediately.
Before/after
Before:
After:
Test plan
Workflow-only change; control flow and tool permissions are unchanged. Will be exercised by the next AI no-backport decision after merge.