ci: trigger CI on merge_group so the merge queue can complete - #83
Merged
Conversation
The repository's default-branch ruleset requires the GitHub Merge Queue, and requires this workflow's Integration and Protocol test jobs as status checks. The queue runs checks against temporary gh-readonly-queue/main/* branches, which only trigger workflows that opt in via the merge_group event. This workflow only had push and pull_request triggers, so no run ever started for queued entries — they sat in AWAITING_CHECKS indefinitely, waiting on required checks that could never execute. Also extend test-integration-cloud-serverless's forked-PR guard to allow merge_group events. Without this, adding the trigger above would make the job run but immediately evaluate its `if` to false and report skipped — still leaving one of the three required checks permanently unsatisfied on queue runs.
jstirnaman
temporarily deployed
to
cloud-serverless
July 28, 2026 22:30 — with
GitHub Actions
Inactive
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 default-branch ruleset requires the GitHub Merge Queue and requires this
workflow's
Integration tests (InfluxDB 3 Core),Integration tests (InfluxDB Cloud Serverless), andProtocol testsjobs as status checks. The queue runschecks against temporary
gh-readonly-queue/main/*branches, which onlytrigger workflows that opt in via the
merge_groupevent.ci.ymlonly hadpushandpull_requesttriggers, so no run ever started for queuedentries — they sat in
AWAITING_CHECKSindefinitely, waiting on requiredchecks that could never execute. Confirmed via the GitHub API: zero Actions
runs exist on any
gh-readonly-queue/*branch, andmergeQueue.entriessatnon-empty with every entry stuck at
AWAITING_CHECKS.merge_group:to the workflow'son:triggers.test-integration-cloud-serverless's forked-PR guard(
if: github.event_name == 'push' || ...) to also allowgithub.event_name == 'merge_group'. Without this, the job would run onqueue events but immediately evaluate its
ifto false and reportskipped — leaving one of the three required checks permanently
unsatisfied on queue runs, same symptom as before.
Related: the ruleset previously also had a
required_deploymentsrule withan empty environment list, which independently blocked the queue with
"Pull request cannot be added to a merge queue that requires deployments
before merging." That's already been removed from the ruleset directly
(no deployment workflow exists in this repo — the
cloud-serverlessenvironment only scopes a test secret, which GitHub's UI mislabels as a
"deployment").
Test plan
actionlint .github/workflows/ci.yml— cleanzizmor .github/workflows/ci.yml— only pre-existing, unrelatedexcessive-permissions warnings
Add read-only ADR and 2026-07-23 e2e testbench results #79, Add tests for write-path error handling and packaging bugs #80) actually progress past
AWAITING_CHECKS