Skip to content

feat(ci): expose last failed batch draft PR from queue-info#1591

Draft
sileht wants to merge 1 commit into
mainfrom
devs/sileht/queue-info-last-failed-draft-pr/expose-last-failed-batch-draft-pr-queue-info--7fe971fe
Draft

feat(ci): expose last failed batch draft PR from queue-info#1591
sileht wants to merge 1 commit into
mainfrom
devs/sileht/queue-info-last-failed-draft-pr/expose-last-failed-batch-draft-pr-queue-info--7fe971fe

Conversation

@sileht

@sileht sileht commented Jun 12, 2026

Copy link
Copy Markdown
Member

mergify ci queue-info prints the merge-queue note payload as JSON and
appends it to $GITHUB_OUTPUT as queue_metadata. A workflow that only
wants the most recent failed batch's draft PR number had to parse that
JSON and dig into previous_failed_batches[-1].draft_pr_number.

Add a second GHA output, last_failed_draft_pr, written next to
queue_metadata. previous_failed_batches is ordered oldest→newest so
the last element is the most recent; the value is that batch's
draft_pr_number as a plain single line, empty when the field is absent
or empty (falsy in a workflow if:).

Single-line key=value format matches the existing test_results_upload
output in junit-process — the value is numeric so no heredoc is needed.

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

Copilot AI review requested due to automatic review settings June 12, 2026 23:12
@mergify mergify Bot had a problem deploying to Mergify Merge Protections June 12, 2026 23:12 Failure
@sileht sileht temporarily deployed to func-tests-live June 12, 2026 23:12 — with GitHub Actions Inactive

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@mergify

mergify Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🔴 2 of 5 protections blocking · waiting on 👀 reviews and 🙋 you

Protection Waiting on
🔴 👀 Review Requirements 👀 reviews and 🙋 you
🔴 🔎 Reviews 👀 reviews
🟢 🤖 Continuous Integration
🟢 Enforce conventional commit
🟢 📕 PR description

🔴 👀 Review Requirements

Waiting for

  • #approved-reviews-by>=2
This rule is failing.
  • any of:
    • #approved-reviews-by>=2
    • author = dependabot[bot]
    • author = mergify-ci-bot
    • author = renovate[bot]

🔴 🔎 Reviews

Waiting for

  • #review-requested = 0
This rule is failing.
  • #review-requested = 0
  • #changes-requested-reviews-by = 0
  • #review-threads-unresolved = 0

@mergify mergify Bot requested a review from a team June 12, 2026 23:19
jd
jd previously approved these changes Jun 13, 2026
@mergify mergify Bot requested a review from a team June 13, 2026 18:41
@mergify

mergify Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

@sileht this pull request is now in conflict 😩

@mergify mergify Bot added the conflict label Jun 16, 2026
`mergify ci queue-info` prints the merge-queue note payload as JSON and
appends it to `$GITHUB_OUTPUT` as `queue_metadata`. A workflow that only
wants the most recent failed batch's draft PR number had to parse that
JSON and dig into `previous_failed_batches[-1].draft_pr_number`.

Add a second GHA output, `last_failed_draft_pr`, written next to
`queue_metadata`. `previous_failed_batches` is ordered oldest→newest so
the last element is the most recent; the value is that batch's
`draft_pr_number` as a plain single line, empty when the field is absent
or empty (falsy in a workflow `if:`).

Single-line `key=value` format matches the existing `test_results_upload`
output in `junit-process` — the value is numeric so no heredoc is needed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I7fe971fe6ccfbb0eb6225e22bc12af4a3306b6fb
@sileht sileht force-pushed the devs/sileht/queue-info-last-failed-draft-pr/expose-last-failed-batch-draft-pr-queue-info--7fe971fe branch from 894be5a to 2616909 Compare June 16, 2026 14:09
@sileht

sileht commented Jun 16, 2026

Copy link
Copy Markdown
Member Author

Revision history

# Type Changes Reason Date
1 initial 894be5a 2026-06-16 14:09 UTC
2 content 894be5a → 2616909 2026-06-16 14:09 UTC

@sileht sileht temporarily deployed to func-tests-live June 16, 2026 14:10 — with GitHub Actions Inactive
@sileht sileht deployed to func-tests-live June 16, 2026 14:10 — with GitHub Actions Active
@mergify mergify Bot dismissed jd’s stale review June 16, 2026 14:10

Pull request has been modified.

@mergify mergify Bot had a problem deploying to Mergify Merge Protections June 16, 2026 14:10 Failure
@mergify mergify Bot removed the conflict label Jun 16, 2026
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.

3 participants