ci(mergify): skip integration deployment test if PR is in merge queue

[Abogical]

If a PR had a new merge commit from main before it was about merged to main, the integration test deployment workflow was triggered and waited for user input to start the workflow. This blocked merge queues unnecessarily.

This PR disables this conditions only if the PR is in the merge queue.

Note that by default merge_conditions is the same as queue_conditions if its not specified. We specify them in this PR without the integ test workflow check, so it would be skipped during merge check.

This change has been made by @Abogical from the Mergify config editor.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

• check-success = Configuration changed

[aws-cdk-automation]

(This review is outdated)

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[kumvprat]

We should consider revert scenarios : What happens if we need to revert this ? Will it bypass the mergify queue itself ?

[Abogical]

@kumvprat I think you can just a regular Github merge to override mergify.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

✅ The pull request has been merged at 72d3029

This pull request spent 42 minutes 49 seconds in the queue, including 30 minutes 32 seconds running CI.
The checks were run in-place.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • ci(mergify): skip integration deployment test if PR is in merge queue #36699
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • ci(mergify): skip integration deployment test if PR is in merge queue #36699
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.