Skip to content

[pre-commit.ci] pre-commit autoupdate#49

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

[pre-commit.ci] pre-commit autoupdate#49
pre-commit-ci[bot] wants to merge 1 commit into
mainfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci
Copy link
Copy Markdown
Contributor

@pre-commit-ci pre-commit-ci Bot commented May 25, 2026

updates:

Summary by Sourcery

Build:

  • Adjust the pre-commit configuration to point the gitleaks hook at tag v8.30.0 instead of v8.30.1.

updates:
- [github.com/gitleaks/gitleaks: v8.30.1 → v8.30.0](gitleaks/gitleaks@v8.30.1...v8.30.0)
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented May 25, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This pull request updates the configured version of the gitleaks pre-commit hook by changing its rev from v8.30.1 to v8.30.0 in the pre-commit configuration file.

Sequence diagram for updated gitleaks pre-commit hook version

sequenceDiagram
  actor Developer
  participant Git as Git
  participant PreCommit as pre_commit
  participant Gitleaks as gitleaks_v8_30_0

  Developer->>Git: git commit
  Git->>PreCommit: run configured hooks
  PreCommit->>Gitleaks: gitleaks (rev v8.30.0)
  Gitleaks-->>PreCommit: scan results
  PreCommit-->>Git: allow or block commit
Loading

File-Level Changes

Change Details Files
Adjust gitleaks pre-commit hook to use version v8.30.0 instead of v8.30.1.
  • Update the gitleaks repo rev field from v8.30.1 to v8.30.0 in the pre-commit configuration
  • Keep all other repos, hooks, and configuration entries unchanged
.pre-commit-config.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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