merge queue: embarking main (3083cc1) and #4133 together

[mergify]

🎉 This pull request has been checked successfully and will be merged. 🎉

Branch main (3083cc1) and #4133 are embarked together for merge.

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

Required conditions of queue default for merge:

• #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• -files=.mergify.yml
• branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• any of:
  • status-success=Quality Gate
  • all of:
    • -files~=^(?!docs/|logo/)
    • -files~=^docs/docs/04-standard-library/[^/]+/[^/]+\.md$

Required conditions to stay in the queue:

• #approved-reviews-by>=1 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• #changes-requested-reviews-by=0 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• #review-threads-unresolved=0 [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133
• branch-protection-review-decision=APPROVED [🛡 GitHub branch protection]
  • feat(compiler): access modifiers #4133

Visit the Mergify Dashboard to check the state of the queue default.

---

More information about Mergify merge queue can be found in the documentation.

Mergify commands

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the queue rules

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

---
pull_requests:
  - number: 4133
...