Run 'make check' on the CI (#833)

hugovk · web-flow · commit 429325ec7d8a · 2022-04-14T11:36:33.000+01:00
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -1,31 +1,26 @@
 name: Tests
 
-on:
-  pull_request:
-  push:
-    branches: main
-  workflow_dispatch:
+on: [pull_request, push, workflow_dispatch]
+
+env:
+  FORCE_COLOR: 1
 
 jobs:
   test:
-    name: test w/ Python ${{ matrix.python-version }}
+    name: test
 
     runs-on: ubuntu-latest
 
-    strategy:
-      matrix:
-        python-version: ["3.10"]
-
     steps:
-      - uses: actions/checkout@v2
-      - uses: actions/setup-python@v2
+      - uses: actions/checkout@v3
+      - uses: actions/setup-python@v3
         with:
-          python-version: ${{ matrix.python-version }}
+          python-version: "3.10"
           cache: pip
-      - name: Install Dependencies
-        run: python3 -m pip install -U pip -r requirements.txt
-      - name: Build Docs
-        run: sphinx-build --color -n -W -b html -d _build/doctrees . _build/html
-      - name: Link Check
-        run: sphinx-build --color -b linkcheck -d _build/doctrees . _build/linkcheck
+      - name: Build docs
+        run: make html
+      - name: Check markup
+        run: make check
+      - name: Link check
+        run: make linkcheck
         continue-on-error: true
diff --git a/compiler.rst b/compiler.rst
@@ -406,7 +406,7 @@ Emission of bytecode is handled by the following macros:
     just like ``ADDOP_O``, but name mangling is also handled; used for
     attribute loading or importing based on name
 ``ADDOP_LOAD_CONST(struct compiler *, PyObject *)``
-    add the `LOAD_CONST` opcode with the proper argument based on the
+    add the ``LOAD_CONST`` opcode with the proper argument based on the
     position of the specified PyObject in the consts table.
 ``ADDOP_LOAD_CONST_NEW(struct compiler *, PyObject *)``
     just like ``ADDOP_LOAD_CONST_NEW``, but steals a reference to PyObject
diff --git a/documenting.rst b/documenting.rst
@@ -1572,8 +1572,8 @@ Using sphinx-build
 ------------------
 
 Sometimes we directly want to execute the sphinx-build tool instead of through
-`make` (although the latter is still the preferred way). In this case, you can
-use the following command line from the `Doc` directory (make sure to install
+``make`` (although the latter is still the preferred way). In this case, you can
+use the following command line from the ``Doc`` directory (make sure to install
 Sphinx_, blurb_ and python-docs-theme_ packages from PyPI)::
 
    sphinx-build -b<builder> . build/<builder>
diff --git a/parser.rst b/parser.rst
@@ -570,7 +570,7 @@ Pegen has some special grammatical elements and rules:
 * Strings with single quotes (') (e.g. ``'class'``) denote KEYWORDS.
 * Strings with double quotes (") (e.g. ``"match"``) denote SOFT KEYWORDS.
 * Upper case names (e.g. ``NAME``) denote tokens in the :file:`Grammar/Tokens` file.
-* Rule names starting with `invalid_` are used for specialized syntax errors.
+* Rule names starting with ``invalid_`` are used for specialized syntax errors.
 
   - These rules are NOT used in the first pass of the parser.
   - Only if the first pass fails to parse, a second pass including the invalid
@@ -611,7 +611,7 @@ As described previously, to avoid exponential time complexity in the parser, mem
 The C parser used by Python is highly optimized and memoization can be expensive both in memory and time. Although
 the memory cost is obvious (the parser needs memory for storing previous results in the cache) the execution time
 cost comes for continuously checking if the given rule has a cache hit or not. In many situations, just parsing it
-again can be faster. Pegen **disables memoization by default** except for rules with the special marker `memo` after
+again can be faster. Pegen **disables memoization by default** except for rules with the special marker ``memo`` after
 the rule name (and type, if present): ::
 
     rule_name[typr] (memo):
diff --git a/tracker.rst b/tracker.rst
@@ -8,20 +8,20 @@ Using the Issue Tracker
 =======================
 
 If you think you have found a bug in Python, you can report it to the
-`issue tracker`_. The `issue tracker`_ is now hosted on Github, alongside
+`issue tracker`_. The `issue tracker`_ is now hosted on GitHub, alongside
 the codebase and pull requests.  Documentation bugs can also be reported there.
 
 If you would like to file an issue about this devguide, please do so at the
 `devguide repo`_.
 
 .. note::
     Python used to use a dedicated `Roundup`_ instance as its issue tracker.
-    That old bug tracker was hosted under the domain `bugs.python.org`
-    (sometimes called `bpo` for short). Currently a read-only version is still
-    available on that domain for historical purposes. All `bpo` data has been
-    migrated to the current `issue tracker`_ on Github.
+    That old bug tracker was hosted under the domain ``bugs.python.org``
+    (sometimes called ``bpo`` for short). Currently a read-only version is still
+    available on that domain for historical purposes. All ``bpo`` data has been
+    migrated to the current `issue tracker`_ on GitHub.
 
-    If you're familiar with `bpo` and would like to learn more about Github
+    If you're familiar with ``bpo`` and would like to learn more about GitHub
     issues, please read this page, and the :doc:`triaging` page as they
     provide good introductory material. There is also a :doc:`gh-faq`
     document to answer some of the more popular questions.
@@ -41,14 +41,14 @@ already been reported.  Checking if the problem is an existing issue will:
 
 To see if an issue already exists, search the bug database using the search box
 above the list of bugs on the issues page. A form-based `advanced search`_ query
-builder is also available on Github to help creating the text query you need.
+builder is also available on GitHub to help creating the text query you need.
 
 Reporting an issue
 ------------------
 
 If the problem you're reporting is not already in the `issue tracker`_, you
 can report it using the green "New issue" button on the right of the search
-box above the list of bugs. If you're not already signed in to Github, it
+box above the list of bugs. If you're not already signed in to GitHub, it
 will ask you to do so now.
 
 First you need to select what kind of problem you want to report. The
@@ -90,7 +90,7 @@ developers, this is covered in the :ref:`triaging` page. You don't need
 to worry about those when reporting issues as a Python user.
 
 You will automatically receive an update each time an action is taken on
-the bug, unless you changed your Github notification settings.
+the bug, unless you changed your GitHub notification settings.
 
 
 Disagreement With a Resolution on the Issue Tracker
