Skip to content

merge queue: embarking main (0c928d7) and #67 together#80

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/0323df27c1
Closed

merge queue: embarking main (0c928d7) and #67 together#80
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/0323df27c1

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Feb 15, 2026

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

Branch main (0c928d7) and #67 are embarked together for merge.

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

  • check-success = coverage
  • check-success = quality
  • check-success = test
  • check-success = test-cross-platform (macos-latest, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (ubuntu-latest, Linux)
  • check-success = test-cross-platform (windows-latest, Windows)
  • all of [🛡 Merge Protections rule CI must pass]:
    • check-success = coverage
    • check-success = quality
    • check-success = test
    • check-success = test-cross-platform (macos-latest, macOS)
    • check-success = test-cross-platform (ubuntu-22.04, Linux)
    • check-success = test-cross-platform (ubuntu-latest, Linux)
    • check-success = test-cross-platform (windows-latest, Windows)
  • all of [🛡 Merge Protections rule Do not merge outdated PRs]:
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-success = DCO
    • check-neutral = DCO
    • check-skipped = DCO
  • any of [🛡 GitHub repository ruleset rule main]:
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections
    • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

---
checking_base_sha: 0c928d788ea009bb9060a78f01009f7096330c6e
previous_failed_batches: []
pull_requests:
  - number: 67
...

dependabot Bot and others added 2 commits February 15, 2026 22:45
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4.6.1 to 6.0.0.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v4.6.1...v6)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-version: 6.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Feb 15, 2026

🧪 CI Insights

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

🟢 All jobs passed!

But CI Insights is watching 👀

@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@mergify mergify Bot closed this Feb 15, 2026
@mergify mergify Bot deleted the mergify/merge-queue/0323df27c1 branch February 15, 2026 22:56
mergify Bot pushed a commit that referenced this pull request Feb 15, 2026
#79)

## Summary
- Add Mergify merge queue with auto-queue rules for approved,
release-plz, and dependabot PRs
- Remove `changes` job and all path-filter conditionals from CI -- all
jobs run unconditionally
- Remove advanced CodeQL workflow in favor of GitHub default code
scanning
- Fix `cargo deny check` to use default config (was referencing
non-existent `deny.ci.toml`)
- Add `label != do-not-merge` exclusion to all auto-queue rules
- Add auto-update rule to keep open PRs rebased against main
- Auto-approve dependabot PRs and disable dependabot's own
rebase-strategy (Mergify handles it)
- Add DCO remediation commit config for contributor-friendly sign-off
recovery

**Note:** The diff appears larger than expected because PR #78 was
merged and the branch was deleted before additional commits were pushed
to the same branch name.

## Post-merge steps
- [x] Add `Mergify Merge Protections` as required status check in branch
protection

## Test plan
- [x] Mergify config validates (Configuration changed check passes)
- [ ] CI jobs run unconditionally (no path filtering)
- [ ] Merge queue processes PRs correctly (PRs #80-84 confirm this)
- [ ] Auto-update rule keeps PRs current with main
- [ ] DCO check passes with remediation config

---------

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
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