Skip to content
Snippets Groups Projects
Select Git revision
  • bump-griffe
  • bump-boto3
  • bump-mlflow-skinny
  • half_precision
  • bump-mkdocstrings-python
  • bump-mkdocs-material
  • bump-numpy
  • main default protected
  • bump-wandb
  • unit-test-polygon-bug
  • bump-albumentations
  • bump-matplotlib
  • bump-scipy
  • bump-tensorboard
  • bump-lxml
  • bump-torchaudio
  • bump-torchvision
  • bump-torch
  • bump-black
  • bump-imageio
  • 0.2.2b2
  • 0.2.2b1
  • 0.2.2a2
  • 0.2.2a1
  • 0.2.1
  • 0.2.0
  • 0.2.0rc12
  • 0.2.0rc11
  • 0.2.0rc10
  • 0.2.0rc9
  • 0.2.0rc8
  • 0.2.0rc7
  • 0.2.0rc6
  • 0.2.0rc5
  • 0.2.0rc4
  • 0.2.0rc3
  • 0.2.0rc2
  • 0.2.0rc1
  • 0.2.0-dev6
  • 0.2.0-dev5
40 results
Blame Permalink
.git-blame-ignore-revs 2.04 KiB 
# 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