docs: fix the links to CI

Author: henryiii

CONTRIBUTING.rst

@@ -102,9 +102,8 @@ Before you submit a pull request, check that it meets these guidelines:
    your new functionality into a function with a docstring, and add the
    feature to the list in `README.rst`.
 
-3. The pull request should work for Python 2.7, and 3.3, 3.4, 3.5.
-   Check `AppVeyor <https://ci.appveyor.com/project/scikit-build/cmake-python-distributions-f3rbb>`_,
-   `CircleCI <https://circleci.com/gh/scikit-build/cmake-python-distributions>`_
+3. The pull request should work for Python 2.7, and 3.5+.
+   Check `GitHub Actions https://github.com/scikit-build/cmake-python-distributions/actions/workflows/build.yml`_
    and `TravisCi <https://travis-ci.org/scikit-build/cmake-python-distributions/pull_requests>`_
    and make sure that the tests pass for all supported Python versions.
 
@@ -115,3 +114,5 @@ Tips
 To run a subset of tests::
 
 	$ pytest tests/test_cmake.py
+    # OR
+    $ nox -s tests -- tests/test_cmake.py

docs/make_a_release.rst

@@ -13,7 +13,7 @@ This is usually done after :ref:`updating_cmake_version`.
 Prerequisites
 -------------
 
-* All CI tests are passing on `AppVeyor`_, `CircleCI`_ and `Travis CI`_.
+* All CI tests are passing on `GitHub Actions`_ and `Travis CI`_.
 
 * You have a `GPG signing key <https://help.github.com/articles/generating-a-new-gpg-key/>`_.
 
@@ -122,8 +122,7 @@ means that ``echo "Hello"`` should be copied and evaluated in the terminal.
 .. _venv: https://docs.python.org/3/library/venv.html
 
 
-.. _AppVeyor: https://ci.appveyor.com/project/scikit-build/cmake-python-distributions-f3rbb/history
-.. _CircleCI: https://circleci.com/gh/scikit-build/cmake-python-distributions
+.. _AppVeyor: https://github.com/scikit-build/cmake-python-distributions/actions/workflows/build.yml
 .. _Travis CI: https://travis-ci.org/scikit-build/cmake-python-distributions/pull_requests
 
 .. _PyPI: https://pypi.org/project/cmake