Added pre-commit and fixed spaces/end-of-file

Author: staticdev

.github/pull_request_template.md

@@ -1,7 +1,7 @@
 Before opening a new issue, please [search][] for a previously filed
 issue to ensure you're not creating a duplicate.
 
-**Note** Bug reports without the following will receive requests for these 
+**Note** Bug reports without the following will receive requests for these
 details to be provided.
 
 ## Version Information

.github/workflows/build.yml

@@ -37,4 +37,3 @@ jobs:
           TOXENV: ${{ matrix.PYTHON.TOXENV }}
           GH_RECORD_MODE: "none"
         continue-on-error: ${{ matrix.PYTHON.ALLOW_FAILURE }}
-        

.gitignore

@@ -24,4 +24,4 @@ tests/id_rsa
 .pytest_cache/
 t.py
 *.pem
-/.python-version
+/.python-version

.pre-commit-config.yaml

@@ -0,0 +1,15 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.0.1
+    hooks:
+    - id: check-added-large-files
+    - id: check-toml
+      types: [toml]
+    - id: check-yaml
+      types: [yaml]
+    - id: end-of-file-fixer
+      types: [text]
+      stages: [commit, push, manual]
+    - id: trailing-whitespace
+      types: [text]
+      stages: [commit, push, manual]

CONTRIBUTING.rst

@@ -5,53 +5,53 @@ Guidelines for Contributing to github3.py
 
 #. Please do **not** use the issue tracker for questions.
 
-#. Please use GitHub's search feature to look for already reported issues 
+#. Please use GitHub's search feature to look for already reported issues
    before reporting your own.
 
-#. Regardless of the magnitude your pull request (a couple lines to a couple 
-   hundred lines), please add your name to the AUTHORS.rst_ file under the 
+#. Regardless of the magnitude your pull request (a couple lines to a couple
+   hundred lines), please add your name to the AUTHORS.rst_ file under the
    heading Contributors.
 
 #. There is a label for issues that should be minor and should be a good way
-   to become acquainted with the project. The easy_ label is the over-arching 
-   way to determine which issues you can dig into without a great deal of 
-   prior knowledge. Most of these issues have a `Pair with Ian`_ label which 
-   means that if you would like, I (@sigmavirus24) will happily pair program 
+   to become acquainted with the project. The easy_ label is the over-arching
+   way to determine which issues you can dig into without a great deal of
+   prior knowledge. Most of these issues have a `Pair with Ian`_ label which
+   means that if you would like, I (@sigmavirus24) will happily pair program
    with you to solve the issue.
 
-#. If you're fixing a bug, please write a regression test. All the tests are 
+#. If you're fixing a bug, please write a regression test. All the tests are
    structured like so::
 
     tests/
     - test_<module_name>.py
         + Test<ClassName>
           - def test_function_or_attribute
 
-   Please do not add your regression test to an existing test, but create a 
-   new one. You can use the form ``test_issue_<number>``. In a docstring add 
-   the link and a short description of the regression issue. For example, if 
-   you found a bug in the class ``Issue``, write your test in the file 
-   ``test_issues.py`` in the class ``TestIssue``. You can place the new test 
+   Please do not add your regression test to an existing test, but create a
+   new one. You can use the form ``test_issue_<number>``. In a docstring add
+   the link and a short description of the regression issue. For example, if
+   you found a bug in the class ``Issue``, write your test in the file
+   ``test_issues.py`` in the class ``TestIssue``. You can place the new test
    in any order, e.g., below all the existing tests, near a related one, &c.
 
-#. If you're adding a new section of the API that does not already exist, 
+#. If you're adding a new section of the API that does not already exist,
    please also add tests to the test suite.
 
-#. If you're adding additional functionality beyond what the API covers, 
-   please open an issue request first and of course add tests to cover the 
+#. If you're adding additional functionality beyond what the API covers,
+   please open an issue request first and of course add tests to cover the
    functionality in the event it is accepted.
 
-   Also, please be certain to add docstrings_ to these functions. Follow the 
+   Also, please be certain to add docstrings_ to these functions. Follow the
    example of other docstrings.
 
 #. In case you haven't caught on, for anything you add, write tests.
 
-#. Be cordial_. Seriously, anyone who isn't cordial will be sent packing, 
-   regardless of the value of their contributions. I will not tolerate some 
+#. Be cordial_. Seriously, anyone who isn't cordial will be sent packing,
+   regardless of the value of their contributions. I will not tolerate some
    contributors creating a hostile environment for others.
 
-#. Rebase your fork/branch if needed and possible before submitting a pull 
-   request. This makes my life easier. If you honestly have no idea what I'm 
+#. Rebase your fork/branch if needed and possible before submitting a pull
+   request. This makes my life easier. If you honestly have no idea what I'm
    talking about, don't worry, I'll take care of it.
 
 #. Please follow pep-0008_. Feel free to also use flake8_ to help.

LICENSE

@@ -1,23 +1,23 @@
-Redistribution and use in source and binary forms, with or without 
-modification, are permitted provided that the following conditions are 
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
 met:
 
-1. Redistributions of source code must retain the above copyright 
+1. Redistributions of source code must retain the above copyright
 notice, this list of conditions and the following disclaimer.
-2. Redistributions in binary form must reproduce the above copyright 
-notice, this list of conditions and the following disclaimer in the 
+2. Redistributions in binary form must reproduce the above copyright
+notice, this list of conditions and the following disclaimer in the
 documentation and/or other materials provided with the distribution.
-3. The name of the author may not be used to endorse or promote products 
+3. The name of the author may not be used to endorse or promote products
 derived from this software without specific prior written permission.
 
-THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
-DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, 
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
-(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
-SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 
-HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 
-STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 
-ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
+ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 POSSIBILITY OF SUCH DAMAGE.

README.rst

@@ -1,7 +1,7 @@
 .. image::
     https://raw.github.com/sigmavirus24/github3.py/master/docs/img/gh3-logo.png
 
-github3.py is a comprehensive, actively developed and extraordinarily stable 
+github3.py is a comprehensive, actively developed and extraordinarily stable
 wrapper around the GitHub API (v3).
 
 Note: This library currently works with Python 3.6+ or pypy3. For older versions, please use version 1.3.0.
@@ -32,8 +32,8 @@ Please read the `CONTRIBUTING`_ document.
 Testing
 ~~~~~~~
 
-You can run either ``pip install -r dev-requirements.txt`` to install the 
-following before testing or simply ``make test-deps``. It is suggested you do 
+You can run either ``pip install -r dev-requirements.txt`` to install the
+following before testing or simply ``make test-deps``. It is suggested you do
 this in a virtual environment. These need to be installed for the tests to run.
 
 - betamax_
@@ -86,11 +86,11 @@ Ian Stapleton Cordasco (sigmavirus24_)
 Contact Options
 ---------------
 
-- Feel free to use the `github3.py`_ tag on Stack Overflow for any questions 
+- Feel free to use the `github3.py`_ tag on Stack Overflow for any questions
   you may have
-- If you dislike Stack Overflow it is preferred that you send an email to 
+- If you dislike Stack Overflow it is preferred that you send an email to
   [email protected]
-- You may also contact (via email_) the author directly with 
+- You may also contact (via email_) the author directly with
   questions/suggestions/comments or if you wish to include sensitive data.
 
 .. _github3.py: http://stackoverflow.com/questions/tagged/github3.py

example-notebooks/all_repositories.ipynb

@@ -129,4 +129,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/contents-api.ipynb

@@ -609,4 +609,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/forking_repositories_by.ipynb

@@ -173,4 +173,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/managing_issues.ipynb

@@ -400,4 +400,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/public_gist_api.ipynb

@@ -159,4 +159,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/retrieving_issues_on_a_repository.ipynb

@@ -366,4 +366,4 @@
    "metadata": {}
   }
  ]
-}
+}

example-notebooks/statuses-api.ipynb

@@ -304,4 +304,4 @@
    "metadata": {}
   }
  ]
-}
+}