Skip to content

merge queue: checking main (25a3bba) and #36138 together#36422

Closed
mergify[bot] wants to merge 8 commits into
mainfrom
mergify/merge-queue/ca4e7923c0
Closed

merge queue: checking main (25a3bba) and #36138 together#36422
mergify[bot] wants to merge 8 commits into
mainfrom
mergify/merge-queue/ca4e7923c0

Conversation

@mergify

@mergify mergify Bot commented Jul 3, 2026

Copy link
Copy Markdown

⏳ The pull request #36138 is queued for merge and currently being checked. ⏳

Branch main (25a3bba) and #36138 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #36138.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 25a3bba2795ca2aba6fa15d7134457bea3c299f9
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 36138
    scopes: []
scopes: []
...

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

  • This PR fixes #123 or Fixes: #123

  • This PR closes #123 or Closes: #123

  • This PR resolves #123 or Resolves: #123

  • Other supported keywords: fix, fixed, close, closed, resolve, resolved
    Option 2: Link via GitHub UI (Note: won't clear the failed check)

  1. Go to the PR → Development section (right sidebar)

  2. Click "Link issue" and select an existing issue

  3. Push a new commit or re-run the workflow to clear the failed check
    Option 3: Use branch naming
    Create a new branch with one of these patterns:

  • 123-feature-description (number at start)

  • issue-123-feature-description (issue-number at start)

  • feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

@github-actions github-actions Bot added the Area : Backend PR changes Java/Maven backend code label Jul 3, 2026
@mergify mergify Bot closed this Jul 3, 2026
@mergify mergify Bot deleted the mergify/merge-queue/ca4e7923c0 branch July 3, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area : Backend PR changes Java/Maven backend code

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant