ci(Mergify): configuration update

[unclesp1d3r]

This change has been made by @unclesp1d3r from the Mergify workflow automation editor.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e44f6099-6dc3-45f9-836c-0b854f97bb67

📥 Commits

Reviewing files that changed from the base of the PR and between 2e446e7 and 70b5b6c.

📒 Files selected for processing (1)

• .mergify.yml

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

---

📝 Walkthrough

Mergify Configuration Initialization

This PR introduces the initial .mergify.yml configuration file to establish automated PR management and merge workflows for the Stringy repository.

Architectural Impact

Merge Queue Architecture: Establishes a centralized merge queue system using Mergify's squash merge strategy. All PRs must pass a comprehensive CI gate consisting of:

• Quality checks
• Multi-version MSRV (Minimum Supported Rust Version) validation across 5 stability tiers
• Cross-platform testing (Linux, macOS, Windows)
• Code coverage verification

PR Workflow Automation: Implements four distinct PR processing rules with differentiated handling:

1. Maintainer PRs: Fast-tracked to queue when labeled with lgtm
2. Dependabot PRs: Auto-approved and queued (excluding release workflow changes)
3. External PRs: Queued only after explicit maintainer approval
4. Automatic sync: Keeps PRs updated with main branch changes

Merge Protection Enforcement:

• Conventional Commit validation: Enforces commit message format (fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?: for all merges to main
• CI gate enforcement: Prevents manual merge bypasses by requiring all checks in success conditions
• Staleness prevention: Blocks merges for PRs more than 10 commits behind main branch

Governance and Semantics

The configuration establishes clear separation between contributor types (maintainers, bots, external) with appropriate approval workflows. The conventional commit enforcement ensures semantic consistency in commit history for future changelog generation and version management.

Walkthrough

Uncommented and enabled Tier 2 and Tier 3 PR processing rules in Mergify configuration, standardized YAML string literal quoting, refined author filter syntax in Tier 3 rules, and reformatted the conventional-commit title regex for clarity without altering validation logic.

Changes

Cohort / File(s)	Summary
Mergify Configuration .mergify.yml	Activated previously commented PR processing tiers (Tier 2, Tier 3); converted quoted check-success entries to unquoted YAML literals; corrected author filter syntax in Tier 3 rules; reformatted conventional-commit regex to multi-line indented form; removed unnecessary quoting in CI/PR-related sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

enhancement

Poem

🔧 Tiers awaken from their slumber deep,
Mergify rules now vigil keep,
YAML quotes shed like winter frost,
Configuration gains, no logic lost! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch mergify/unclesp1d3r/I36325320ac5c4ee08589444dff0efeb878056b83

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Updates the repository's Mergify configuration used to gate and queue merges into main, primarily by reformatting conditions and protections.

Changes:

• Reformats queue rule CI merge_conditions entries (removes quoting/blank lines).
• Reformats maintainer/external PR rule conditions (removes quoting, adjusts YAML formatting).
• Reformats merge protections, including the conventional-commit title regex and CI protection description.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!