Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
D
DAN
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Container Registry
Operate
Terraform modules
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Automatic Text Recognition
DAN
Commits
509ab8c4
Verified
Commit
509ab8c4
authored
10 months ago
by
Yoann Schneider
Browse files
Options
Downloads
Patches
Plain Diff
Ignore license related revisions in git blame
parent
5079aad2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!412
Ignore license related revisions in git blame
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.git-blame-ignore-revs
+41
-0
41 additions, 0 deletions
.git-blame-ignore-revs
with
41 additions
and
0 deletions
.git-blame-ignore-revs
0 → 100644
+
41
−
0
View file @
509ab8c4
# This file contains revisions to be ignored by git blame.
# These revisions are expected to be formatting-only changes.
#
# Calling `git blame --ignore-revs-file .git-blame-ignore-revs` will
# tell git blame to ignore changes made by these revisions when assigning
# assigning blame, as if the change never happened.
#
# You can enable this as a default for your local repository by running
# `git config blame.ignoreRevsFile .git-blame-ignore-revs`
# This will probably be automatically picked by your IDE
# (VSCode+GitLens and JetBrains products are confirmed to this)
#
# Important: if you are switching to the branch without this file,
# `git blame` will fail with an error
#
# Guidelines:
# - Only large automated refactorings are expected to be included in this file.
# Do not add new revision just because it feels unimportant
# - When adding sinle revision use inline comment to link relevant issue/MR
# Example:
## d4a8b7307acc2dc8a8833ccfa65426ad28b3ffc9 # https://gitlab.teklia.com/atr/dan/issues/12345
# - When adding multiple revisions precede each addition (this could be multiple revisions) with a link to
# line with word START and link to relevant issue/MR and conclude with line END and link to the
# same issue/MR
# Example:
# # START https://gitlab.teklia.com/atr/dan/issues/12345
# 6f0bd2d8a1e6cd2e794cd39976e9756e0c85ac66
# d53974df11dbc22cbea9dc7dcbc9896c25979a27
# ... <rest of the list>
# # END https://gitlab.teklia.com/atr/dan/issues/12345
# - Please append new lines to the end of the file, no matter of real chronological
# order of revisions
# - Since this is using hashes for reformatting it might be a good idea to update
# this file in separate MR when relevant changes already landed in master. By
# utilizing this manner you will be safe from random rebase/squash issues
# - Only put full 40-character hashes on this list
# START https://gitlab.teklia.com/atr/dan/-/merge_requests/408
05db961d87448647e8f59f6b728b321b17263042
838c7df40b3c6ba223008416e2a654fe40bfcf4a
# END https://gitlab.teklia.com/atr/dan/-/merge_requests/408
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment