Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DEFRA/water-abstraction-team#37
This change creates a
.git-blame-ignore-revs
file containing the sha of the commit that switched from using ES Lint and semi-standard to plain old JS standard. This will hide this commit ingit blame
(given the correct config option) and in GitHub's blame view.GitLens
If you use a tool such as GitLens which shows
git blame
info in the IDE, you can check its effect by first viewing a file which was changed, eg.src/lib/camel-case-keys.js
:Now pull down the branch and enter the following command in your
water-abstraction-service
folder to configuregit blame
to use.git-blame-ignore-revs
:Close and re-open the file and you'll see the output of
git blame
now ignores that commit:Note that the configuration option will break
git blame
if you revert to a branch which doesn't have.git-blame-ignore-revs
. You can remove it by running the following command in yourwater-abstraction-service
folder:We recommend you don't set
blame.ignorerevsfile
globally as this will stopgit blame
from working for any folder which doesn't have a.git-blame-ignore-revs
file! Better to set the option for each folder individually as and when they're updated with.git-blame-ignore-revs
.GitHub
The difference in GitHub's blame view can be seen here:
Before:
After: