Skip to content

Update README.md to include GIT hooks configuration#324

Merged
guibranco merged 2 commits intomainfrom
guibranco-patch-1
Jan 14, 2026
Merged

Update README.md to include GIT hooks configuration#324
guibranco merged 2 commits intomainfrom
guibranco-patch-1

Conversation

@guibranco
Copy link
Owner

@guibranco guibranco commented Jan 14, 2026

📑 Description

Update README.md to include GIT hooks configuration

✅ Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

☢️ Does this introduce a breaking change?

  • Yes
  • No

Summary by Sourcery

Documentation:

  • Add README instructions for setting a per-repository Git hooks path, including using a .githooks directory and the corresponding git config command.

Summary by CodeRabbit

Documentation

  • Added configuration guide for setting custom git hooks path.
  • Enhanced API disable documentation with environment variable examples (Windows and non-Windows) and detailed behavior when API calls are disabled.

✏️ Tip: You can customize this high-level summary in your review settings.

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Jan 14, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the README to document how to configure a custom Git hooks path (e.g., using a .githooks directory) via git config.

File-Level Changes

Change Details Files
Document configuration of a custom Git hooks path for the repository.
  • Add a new subsection explaining the default Git hooks path at .git/hooks
  • Describe how to override the default by using a .githooks directory at the project root
  • Provide the exact git config core.hooksPath '.githooks' command for per-repository configuration
README.md

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

@guibranco guibranco enabled auto-merge (squash) January 14, 2026 11:03
@gstraccini gstraccini bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label Jan 14, 2026
@github-actions github-actions bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 14, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 14, 2026

Caution

Review failed

The pull request is closed.

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Walkthrough

Documentation updates to README.md adding a new "Set GIT hooks path" configuration section describing core.hooksPath override, and expanding the "Disable API Calls" section with explicit environment variable examples for both Linux/Mac and Windows platforms.

Changes

Cohort / File(s) Summary
Documentation Updates
README.md
Added "Set GIT hooks path" configuration section (duplicated instance); expanded "Disable API Calls" section with environment variable examples (DOTNET_AICOMMITMESSAGE_DISABLE_API) for cross-platform usage and resulting behavior description

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A documentation hop and skip,
With hooks and config tips to flip,
Environment vars now clearly shown,
For Windows, Mac—no stone left alone!
Words arranged in perfect way,
Our README gleams bright today! ✨



📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c37afc and d03988b.

📒 Files selected for processing (1)
  • README.md

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Contributor

@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 found 1 issue, and left some high level feedback:

  • Consider making the hooks path use POSIX-style separators (e.g. .git/hooks/) or clarifying that \.git\hooks\ is Windows-specific so the instructions are unambiguous across platforms.
  • The sentence 'If you want to override, or use the .githooks directory at the root level of your project, you will need to configure that.' could be tightened (e.g. remove the comma after 'override' and specify 'override the default path') for clearer readability.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider making the hooks path use POSIX-style separators (e.g. `.git/hooks/`) or clarifying that `\.git\hooks\` is Windows-specific so the instructions are unambiguous across platforms.
- The sentence 'If you want to override, or use the `.githooks` directory at the root level of your project, you will need to configure that.' could be tightened (e.g. remove the comma after 'override' and specify 'override the default path') for clearer readability.

## Individual Comments

### Comment 1
<location> `README.md:234` </location>
<code_context>

+### Set GIT hooks path
+
+By default the GIT hooks path is defined at repository level to `.git\hooks\`
+If you want to override, or use the `.githooks` directory at the root level of your project, you will need to configure that.
+
</code_context>

<issue_to_address>
**suggestion (typo):** Improve grammar in the sentence describing the default GIT hooks path.

For example: "By default, the GIT hooks path is defined at the repository level as `.git\hooks\`."

```suggestion
By default, the GIT hooks path is defined at the repository level as `.git\hooks\`.
```
</issue_to_address>

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.

@deepsource-io
Copy link

deepsource-io bot commented Jan 14, 2026

Here's the code health analysis summary for commits 7c37afc..d03988b. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Test coverage LogoTest coverage✅ SuccessView Check ↗
DeepSource Secrets LogoSecrets✅ SuccessView Check ↗
DeepSource Docker LogoDocker✅ SuccessView Check ↗
DeepSource C# LogoC#✅ SuccessView Check ↗

Code Coverage Report

MetricAggregateC#
Branch Coverage46.2%46.2%
Condition Coverage46.2%46.2%
Composite Coverage46.8%46.8%
Line Coverage47%47%

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Co-authored-by: sourcery-ai[bot] <58596630+sourcery-ai[bot]@users.noreply.github.com>
@github-actions
Copy link
Contributor

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs
2026-01-14T11:04:46Z INF scanning for exposed secrets...
11:04AM INF 259 commits scanned.
2026-01-14T11:04:46Z INF scan completed in 74.3ms
2026-01-14T11:04:46Z INF no leaks found

@sonarqubecloud
Copy link

@guibranco guibranco merged commit a1dd09c into main Jan 14, 2026
26 of 27 checks passed
@guibranco guibranco deleted the guibranco-patch-1 branch January 14, 2026 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant