Skip to content

ci: [pre-commit.ci] pre-commit autoupdate#16

Open
pre-commit-ci[bot] wants to merge 1 commit intomainfrom
pre-commit-ci-update-config
Open

ci: [pre-commit.ci] pre-commit autoupdate#16
pre-commit-ci[bot] wants to merge 1 commit intomainfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci
Copy link
Contributor

@pre-commit-ci pre-commit-ci bot commented Sep 22, 2025

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 22, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

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

@myakove-bot
Copy link
Collaborator

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

Note: You are an auto-verified user. Your PRs will be automatically verified and may be auto-merged when all requirements are met.

🔄 Automatic Actions

  • Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
  • Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
  • Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
  • Pre-commit Checks: pre-commit runs automatically if .pre-commit-config.yaml exists
  • Branch Labeling: Branch-specific labels are applied to track the target branch
  • Auto-verification: Auto-verified users have their PRs automatically marked as verified

📋 Available Commands

PR Status Management

  • /wip - Mark PR as work in progress (adds WIP: prefix to title)
  • /wip cancel - Remove work in progress status
  • /hold - Block PR merging (approvers only)
  • /hold cancel - Unblock PR merging
  • /verified - Mark PR as verified
  • /verified cancel - Remove verification status

Review & Approval

  • /lgtm - Approve changes (looks good to me)
  • /approve - Approve PR (approvers only)
  • /automerge - Enable automatic merging when all requirements are met (maintainers and approvers only)
  • /assign-reviewers - Assign reviewers based on OWNERS file
  • /assign-reviewer @username - Assign specific reviewer
  • /check-can-merge - Check if PR meets merge requirements

Testing & Validation

  • /retest tox - Run Python test suite with tox
  • /retest all - Run all available tests

Container Operations

  • /build-and-push-container - Build and push container image (tagged with PR number)
    • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

  • /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
    • Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

  • /<label-name> - Add a label to the PR
  • /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

  1. Approval: /approve from at least one approver
  2. LGTM Count: Minimum 0 /lgtm from reviewers
  3. Status Checks: All required status checks must pass
  4. No Blockers: No WIP, hold, or conflict labels
  5. Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

Reviewers:

Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve
  • automerge

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is automatically removed on each new commit
  • Cherry-picking: Cherry-pick labels are processed when the PR is merged
  • Container Builds: Container images are automatically tagged with the PR number
  • Permission Levels: Some commands require approver permissions
  • Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

@myakove-bot myakove-bot enabled auto-merge (squash) September 22, 2025 20:02
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 31ba665 to 2c416b3 Compare September 29, 2025 19:37
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 5d5cddf to f988b59 Compare October 13, 2025 19:58
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from f988b59 to 406c324 Compare October 20, 2025 21:54
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 406c324 to 7ed56bf Compare October 27, 2025 19:42
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 7ed56bf to 808fd60 Compare November 3, 2025 20:04
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 7c86a56 to ccbbf27 Compare November 17, 2025 19:50
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from ccbbf27 to 4d204fb Compare November 24, 2025 20:08
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from edd3992 to b76d5d4 Compare December 8, 2025 20:10
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from cc4ee21 to 875b7b3 Compare December 22, 2025 19:45
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from 875b7b3 to 4c2558f Compare January 12, 2026 19:53
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 989c2f6 to 2740baf Compare January 26, 2026 20:01
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch 2 times, most recently from 5c66d22 to b53323f Compare February 16, 2026 19:47
updates:
- [github.com/astral-sh/ruff-pre-commit: v0.13.0 → v0.15.2](astral-sh/ruff-pre-commit@v0.13.0...v0.15.2)
- [github.com/gitleaks/gitleaks: v8.28.0 → v8.30.0](gitleaks/gitleaks@v8.28.0...v8.30.0)
- [github.com/pre-commit/mirrors-mypy: v1.18.1 → v1.19.1](pre-commit/mirrors-mypy@v1.18.1...v1.19.1)
@pre-commit-ci pre-commit-ci bot force-pushed the pre-commit-ci-update-config branch from b53323f to 7787809 Compare February 23, 2026 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant