Skip to content

feat: put the batch id in the generate-prs run name#42

Merged
gjtorikian merged 1 commit into
mainfrom
feat/run-name-batch-id
Jun 25, 2026
Merged

feat: put the batch id in the generate-prs run name#42
gjtorikian merged 1 commit into
mainfrom
feat/run-name-batch-id

Conversation

@gjtorikian

Copy link
Copy Markdown
Collaborator

Summary

Sets a top-level run-name on generate-prs.yml so each workflow_dispatch run's display title is Generate PRs (batch <id>).

This lets the SDK bot dashboard's active-batch card identify this batch's Actions run by matching run.display_title against the batch id, instead of the previous best-effort "newest/earliest dispatch run near the batch timestamp" heuristic — which can link to an unrelated dispatch when several land while a batch is open (or when the batch's run isn't on the first page of results). Non-dispatch runs keep the plain Generate PRs name.

Pairs with the dashboard-side change in sdk-automation-bot (matches on display_title, falls back to the workflow page when no run matches).

Test plan

  • run-name expression validated as well-formed YAML; uses standard Actions expression syntax (inputs.batch_id && format(...) || 'Generate PRs'). No job logic changed.

🤖 Generated with Claude Code

Set run-name to "Generate PRs (batch <id>)" for workflow_dispatch runs so
the SDK bot dashboard can identify THIS batch's Actions run by name
(run.display_title) instead of guessing by timestamp — which can link to
an unrelated dispatch when several land while a batch is open. Non-dispatch
runs keep the plain "Generate PRs" name.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented Jun 25, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates the GitHub Actions display name for generated PR batches. The main changes are:

  • Added a workflow-level run-name to generate-prs.yml.
  • Included inputs.batch_id in dispatch run titles.
  • Kept Generate PRs as the fallback title when no batch id is present.

Confidence Score: 5/5

The workflow naming change is isolated to the GitHub Actions display title and leaves the job logic unchanged.

The changed workflow adds the expected top-level run-name expression, preserves the fallback title when no batch id is available, and keeps the jobs section unchanged.

No files need additional attention.

T-Rex T-Rex Logs

What T-Rex did

  • Reviewed the base workflow snapshot to confirm there is no workflow-level run-name and that the workflow shape and job IDs are as expected.
  • Compared the after-snapshot results to verify the run-name expression is set to Generate PRs (with batch when batch_id is provided), that jobs_equal_to_base is true, and that the expression outputs cover populated, empty, and missing batch IDs.

View all artifacts

T-Rex Ran code and verified through T-Rex

Reviews (1): Last reviewed commit: "feat: put the batch id in the generate-p..." | Re-trigger Greptile

@gjtorikian gjtorikian merged commit be50632 into main Jun 25, 2026
6 checks passed
@gjtorikian gjtorikian deleted the feat/run-name-batch-id branch June 25, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant