Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure we hide configured commits #25

Open
epage opened this issue Sep 12, 2022 · 2 comments
Open

Ensure we hide configured commits #25

epage opened this issue Sep 12, 2022 · 2 comments
Labels
enhancement Improve the expected

Comments

@epage
Copy link
Collaborator

epage commented Sep 12, 2022

Users are able to hide specific commits from blame. I'm guessing git2 isn't doing that for us and we'll need to implement it ourselves.

@epage epage added the enhancement Improve the expected label Sep 12, 2022
@epage epage added this to the 0.1 - Basic Blame milestone Sep 12, 2022
@epage
Copy link
Collaborator Author

epage commented Oct 26, 2022

https://git-scm.com/docs/git-config#Documentation/git-config.txt-blameignoreRevsFile

Ignore revisions listed in the file, one unabbreviated object name per line, in git-blame[1]. Whitespace and comments beginning with # are ignored. This option may be repeated multiple times. Empty file names will reset the list of ignored revisions. This option will be handled before the command line option --ignore-revs-file.

@epage
Copy link
Collaborator Author

epage commented Oct 26, 2022

Huh, not seeing support for this in git2. Unless its a feature we have to implement on top somehow (e.g. checking the Oid and doing a second blame), I'm assuming the best we can do is to just mark the line as unblameable.

@epage epage removed this from the 0.1 - Basic Blame milestone Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve the expected
Projects
None yet
Development

No branches or pull requests

1 participant