Run pre-commit to fix end-of-file-fixer and trailing-whitespace (#3418)

* Run pre-commit to fix end-of-file-fixer and trailing-whitespace

* Add git blame ignore revisions file

* Update .git-blame-ignore-revs

Author: goanpeca

.git-blame-ignore-revs

@@ -0,0 +1,4 @@
+# Run this command to always ignore formatting commits in `git blame`
+# git config blame.ignoreRevsFile .git-blame-ignore-revs
+
+# Run pre-commit to fix end-of-file-fixer and trailing-whitespace

.github/pr-labeler-config.yml

@@ -16,7 +16,7 @@ ci:
 # Add 'examples' to any changes within 'examples' folder
 examples:
   - changed-files:
-    - any-glob-to-any-file: examples/** 
+    - any-glob-to-any-file: examples/**
 
 # Add 'base' to any changes within 'base' folder
 "module: base":
@@ -26,17 +26,17 @@ examples:
 # Add 'contrib' to any changes within 'contrib' folder
 "module: contrib":
   - changed-files:
-    - any-glob-to-any-file: ignite/contrib/**/* 
+    - any-glob-to-any-file: ignite/contrib/**/*
 
 # Add 'distributed' to any changes within 'distributed' folder
 "module: distributed":
   - changed-files:
-    - any-glob-to-any-file: ignite/distributed/**/* 
+    - any-glob-to-any-file: ignite/distributed/**/*
 
 # Add 'engine' to any changes within 'engine' folder
 "module: engine":
   - changed-files:
-    - any-glob-to-any-file: ignite/engine/**/* 
+    - any-glob-to-any-file: ignite/engine/**/*
 
 # Add 'handlers' to any changes within 'handlers' folder
 "module: handlers":
@@ -48,8 +48,8 @@ examples:
   - changed-files:
     - any-glob-to-any-file: ignite/metrics/**/*
 
-  - 
+  -
 # Add 'utils' to any changes within 'utils' module
 "module: utils":
   - changed-files:
-    - any-glob-to-any-file: ignite/utils.py 
+    - any-glob-to-any-file: ignite/utils.py

.github/workflows/discord_issues.yml

@@ -26,5 +26,5 @@ jobs:
           issue_number: ${{ github.event.inputs.issue_number || github.event.issue.number }}
           issue_comment: Hey 👋, I've just created a [thread]($THREAD_LINK$) for this issue on [PyTorch-Ignite Discord](https://pytorch-ignite.ai/chat) where you can quickly talk to the community on the topic.
           discord_message: New issue created in `${{ github.repository }}`:<https://github.com/${{ github.repository }}/issues/${{ github.event.issue.number }}>
-          
-      
+
+

.github/workflows/discord_pull_requests.yaml

@@ -26,4 +26,3 @@ jobs:
           issue_number: ${{ github.event.inputs.pull_request_number || github.event.pull_request.number }}
           issue_comment: Hey 👋, I've just created a [thread]($THREAD_LINK$) for this pull request on [PyTorch-Ignite Discord](https://pytorch-ignite.ai/chat) where you can quickly talk to the community on the topic.
           discord_message: New PR created in `${{ github.repository }}`:<https://github.com/${{ github.repository }}/pull/${{ github.event.pull_request_number || github.event.pull_request.number }}>
-

.github/workflows/stable-release-pypi.yml

@@ -32,4 +32,3 @@ jobs:
           twine --version
           twine check dist/*
           TWINE_USERNAME="${{ secrets.PYPI_USER }}" TWINE_PASSWORD="${{ secrets.PYPI_TOKEN }}" twine upload --verbose dist/*
-

.github/workflows/tpu-tests.yml

@@ -72,7 +72,7 @@ jobs:
           ## Install torch & xla and torchvision
           pip install --pre torch torchvision --index-url https://download.pytorch.org/whl/nightly/cpu
           pip install https://storage.googleapis.com/pytorch-xla-releases/wheels/tpuvm/torch_xla-nightly-cp310-cp310-linux_x86_64.whl
-          
+
           # Check installation
           python -c "import torch"
 

CITATION

@@ -5,4 +5,4 @@
   publisher = {GitHub},
   journal = {GitHub repository},
   howpublished = {\url{https://github.com/pytorch/ignite}},
-}
+}

CONTRIBUTING.md

@@ -80,7 +80,7 @@ conda activate pytorch-ignite-dev
 
 ### Installation
 
-1) Make a fork of the repository on the GitHub (see [here](https://github.com/firstcontributions/first-contributions#fork-this-repository) for details). 
+1) Make a fork of the repository on the GitHub (see [here](https://github.com/firstcontributions/first-contributions#fork-this-repository) for details).
 As a result, for example your username is `happy-ignite-developer`, then you should be able to see your fork on the GitHub, e.g https://github.com/happy-ignite-developer/ignite.git
 
 2) Clone your fork locally and setup `upstream`. Assuming your username is `happy-ignite-developer`: