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 (550b32d) and [#250 + #251] together #252

Closed
wants to merge 4 commits into from

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Aug 9, 2024

🎉 This combination of pull requests has been checked successfully and will be merged soon. 🎉

Branch main (550b32d) and [#250 + #251] are embarked together for merge.

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

Required conditions of queue deps-update for merge:

  • check-success=Good to merge
  • any of [🛡 GitHub branch protection]:
    • check-success=Good to merge
    • check-neutral=Good to merge
    • check-skipped=Good to merge

Required conditions to stay in the queue:

---
previous_failed_batches: []
pull_requests:
  - number: 250
  - number: 251
...

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@stylistic/[email protected] None 0 528 kB eslint-stylistic-bot
npm/[email protected] environment, filesystem 0 198 kB ai
npm/[email protected] None 0 5.71 MB adamwathan, malfaitrobin, reinink

🚮 Removed packages: npm/@stylistic/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Copy link

sonarcloud bot commented Aug 9, 2024

@mergify mergify bot closed this Aug 9, 2024
@mergify mergify bot deleted the mergify/merge-queue/178d574330 branch August 9, 2024 16:18
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.

0 participants