Skip to content

Conversation

@tiagolobocastro
Copy link
Member

No description provided.

@tiagolobocastro tiagolobocastro requested a review from a team as a code owner December 8, 2025 12:08
@tiagolobocastro
Copy link
Member Author

@mergify queue

@mergify
Copy link
Contributor

mergify bot commented Dec 8, 2025

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at a013894

@mergify
Copy link
Contributor

mergify bot commented Dec 8, 2025

Merge Queue Status

✅ The pull request has been merged at e8313ea

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

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of [🛡 GitHub branch protection]:
    • check-success = ci
    • check-neutral = ci
    • check-skipped = ci
  • any of [🛡 GitHub branch protection]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

@mergify mergify bot added the queued label Dec 8, 2025
@mergify mergify bot merged commit a013894 into develop Dec 8, 2025
15 checks passed
@mergify mergify bot deleted the rel-0122 branch December 8, 2025 12:28
@mergify mergify bot removed the queued label Dec 8, 2025
@mergify
Copy link
Contributor

mergify bot commented Dec 8, 2025

🧪 CI Insights

Here's what we observed from your CI run for e8313ea.

🟢 All jobs passed!

But CI Insights is watching 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants