Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge queue: embarking main (e32a5a0) and #26 together #27

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 12, 2025

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

Branch main (e32a5a0) and #26 are embarked together for merge.

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

  • all of:
    • check-success=linters
    • check-success=test
    • check-success=test-annotations
  • all of:
    • schedule=Mon-Fri 09:00-17:30[Europe/Paris]
    • not:
      • any of:
        • current-datetime = XXXX-01-01T00:00/XXXX-01-01T23:59[Europe/Paris]
        • current-datetime = XXXX-05-01T00:00/XXXX-05-01T23:59[Europe/Paris]
        • current-datetime = XXXX-05-08T00:00/XXXX-05-08T23:59[Europe/Paris]
        • current-datetime = XXXX-07-14T00:00/XXXX-07-14T23:59[Europe/Paris]
        • current-datetime = XXXX-08-15T00:00/XXXX-08-15T23:59[Europe/Paris]
        • current-datetime = XXXX-11-01T00:00/XXXX-11-01T23:59[Europe/Paris]
        • current-datetime = XXXX-11-11T00:00/XXXX-11-11T23:59[Europe/Paris]
        • current-datetime = XXXX-12-25T00:00/XXXX-12-25T23:59[Europe/Paris]
  • all of [🛡 Merge Protections rule Changelog requirements]:
  • all of [🛡 Merge Protections rule Enforce conventional commit]:
  • all of [🛡 Merge Protections rule 🔎 Reviews]:
  • any of [🛡 GitHub repository ruleset rule]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

---
previous_failed_batches: []
pull_requests:
  - number: 26
...

jd and others added 2 commits February 12, 2025 10:08
The current code uploads in a different endpoint and the test is getting
a 404.

The Mergify CLI works differently and does not fail on upload issues to
avoid blocking user CI; adapt the scenario.

Change-Id: I86797df95e04d6abc2858c57346e73f04ada430d
@mergify mergify bot closed this Feb 12, 2025
@mergify mergify bot deleted the mergify/merge-queue/b070568335 branch February 12, 2025 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant