merge queue: checking main (f8dddf8), #36793 and #36767 together

[mergify]

✨ Merge queue reset: an external action moved the base branch head to f8e86de. The pull request #36767 has been requeued. ✨

Branch main (f8dddf8), #36793 and #36767 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #36767.
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:

• any of [🛡 GitHub branch protection]:
  • check-neutral = Finalize / Final Status
  • check-skipped = Finalize / Final Status
  • check-success = Finalize / Final Status
• any of [🛡 GitHub branch protection]:
  • check-neutral = Initialize / Initialize
  • check-skipped = Initialize / Initialize
  • check-success = Initialize / Initialize
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • fix(content-drive): align keyword search with Content Search index query #36688 #36767
• github-review-approved [🛡 GitHub branch protection]
  • fix(content-drive): align keyword search with Content Search index query #36688 #36767

Required conditions to stay in the queue:

• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • fix(content-drive): align keyword search with Content Search index query #36688 #36767
• github-review-approved [🛡 GitHub branch protection]
  • fix(content-drive): align keyword search with Content Search index query #36688 #36767
• any of [🛡 GitHub branch protection]:
  • check-success = Finalize / Final Status
  • check-neutral = Finalize / Final Status
  • check-skipped = Finalize / Final Status
• any of [🛡 GitHub branch protection]:
  • check-success = Initialize / Initialize
  • check-neutral = Initialize / Initialize
  • check-skipped = Initialize / Initialize

---
checking_base_sha: 30c3adcc2c5def2106b62bfffec8c15ae226c13d
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 36767
    scopes: []
scopes: []
...

[github-actions]

❌ 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:

• Fixes #123 or Closes #123 — same-repo issue
• Fixes org/repo#123 or Closes org/repo#123 — cross-repo or private issue
• Closes https://github.com/org/repo/issues/123 — full GitHub URL
• 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

[mergify]

Merge queue reset: an external action moved the base branch head to f8e86de