Skip to content

chore: add .git-blame-ignore-revs file - #195

Merged
i582 merged 1 commit into
mainfrom
danil42russia/git-blame-ignore-revs
Jun 21, 2026
Merged

chore: add .git-blame-ignore-revs file#195
i582 merged 1 commit into
mainfrom
danil42russia/git-blame-ignore-revs

Conversation

@Danil42Russia

@Danil42Russia Danil42Russia commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Summary by CodeRabbit

  • Chores
    • Added a Git configuration file to improve code review workflows by instructing git blame to ignore specified mechanical/formatting commits.

@coderabbitai

This comment was marked as low quality.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.git-blame-ignore-revs:
- Line 10: The git config commands in the .git-blame-ignore-revs file use
non-standard syntax that will fail when executed. On line 10, remove the word
"set" from the git config command and use the standard syntax of "git config
[--local] <key> <value>". On line 12, replace "git config unset" with the
correct flag-based syntax "git config --unset <key>" to properly unset the
configuration value. Ensure both commands follow the standard git config command
format.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 74244eff-18bc-475b-9378-26c6d5fdddcd

📥 Commits

Reviewing files that changed from the base of the PR and between 0e3bcce and 6b8f489.

📒 Files selected for processing (1)
  • .git-blame-ignore-revs

Comment thread .git-blame-ignore-revs
# 3) <full commit SHA>
#
# Configure once per clone:
# git config set blame.ignoreRevsFile .git-blame-ignore-revs

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Correct the git config command syntax.

Lines 10 and 12 use non-standard git config syntax that will fail:

  • Line 10 uses git config set ... but the standard syntax is git config [--local] <key> <value> (without set)
  • Line 12 uses git config unset ... but the standard syntax is git config --unset <key> (with --unset flag, not just unset)

Users following these instructions will encounter command errors.

🔧 Proposed fix for git command syntax
# Configure once per clone:
-#   git config set blame.ignoreRevsFile .git-blame-ignore-revs
+#   git config --local blame.ignoreRevsFile .git-blame-ignore-revs
# Disable local config:
-#   git config unset blame.ignoreRevsFile
+#   git config --unset blame.ignoreRevsFile

Also applies to: 12-12

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.git-blame-ignore-revs at line 10, The git config commands in the
.git-blame-ignore-revs file use non-standard syntax that will fail when
executed. On line 10, remove the word "set" from the git config command and use
the standard syntax of "git config [--local] <key> <value>". On line 12, replace
"git config unset" with the correct flag-based syntax "git config --unset <key>"
to properly unset the configuration value. Ensure both commands follow the
standard git config command format.

@Danil42Russia
Danil42Russia force-pushed the danil42russia/git-blame-ignore-revs branch from 6b8f489 to 4525555 Compare June 19, 2026 20:55
@i582
i582 merged commit 311dc33 into main Jun 21, 2026
3 checks passed
@i582
i582 deleted the danil42russia/git-blame-ignore-revs branch June 21, 2026 01:00
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.

2 participants