Deploying to gh-pages from @ fd570dd 🚀

_sources/implementation.rst.txt

@@ -78,11 +78,12 @@ which should reflect the expected change in the ontology resource based on the c
 The title for the pull request generated corresponds to the issue that triggered its generation. If the issue is edited, 
 the same pull request is updated.
 
-Trigger QC checks
+Trigger QC Checks
 """""""""""""""""
-If the pull request should trigger the GitHub workflow for the ontology repository to run QC checks,
-follow the following steps:
-1. Go to the `Settings` tab => `Secrets and variables` => `Actions` and
-add a new repository secret with the name `GH_TOKEN` and the value of the personal access token.
-For more information on personal access tokens, see `here <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic>`_.
-2. The `token: ${{ secrets.GH_TOKEN }}` in the workflow file should be uncommented.
+
+If the pull request should trigger the GitHub workflow for the ontology repository to run QC checks, follow the following steps:
+
+1. Go to the `Settings` tab => `Secrets and variables` => `Actions` and add a new repository secret with the name `GH_TOKEN` and the value of the personal access token.
+   For more information on personal access tokens, see `here <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic>`_.
+
+2. The ``token: ${{ secrets.GH_TOKEN }}`` in the workflow file should be uncommented.

implementation.html

@@ -52,7 +52,7 @@
 <li class="toctree-l2"><a class="reference internal" href="#step-2-take-it-for-a-spin">Step 2: Take it for a spin!</a><ul>
 <li class="toctree-l3"><a class="reference internal" href="#create-a-new-issue">Create a new issue</a></li>
 <li class="toctree-l3"><a class="reference internal" href="#pull-request">Pull request</a></li>
-<li class="toctree-l3"><a class="reference internal" href="#trigger-qc-checks">Trigger QC checks</a></li>
+<li class="toctree-l3"><a class="reference internal" href="#trigger-qc-checks">Trigger QC Checks</a></li>
 </ul>
 </li>
 </ul>
@@ -167,13 +167,13 @@ <h3>Pull request<a class="headerlink" href="#pull-request" title="Permalink to t
 the same pull request is updated.</p>
 </section>
 <section id="trigger-qc-checks">
-<h3>Trigger QC checks<a class="headerlink" href="#trigger-qc-checks" title="Permalink to this heading"></a></h3>
-<p>If the pull request should trigger the GitHub workflow for the ontology repository to run QC checks,
-follow the following steps:
-1. Go to the <cite>Settings</cite> tab =&gt; <cite>Secrets and variables</cite> =&gt; <cite>Actions</cite> and
-add a new repository secret with the name <cite>GH_TOKEN</cite> and the value of the personal access token.
-For more information on personal access tokens, see <a class="reference external" href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic">here</a>.
-2. The <cite>token: ${{ secrets.GH_TOKEN }}</cite> in the workflow file should be uncommented.</p>
+<h3>Trigger QC Checks<a class="headerlink" href="#trigger-qc-checks" title="Permalink to this heading"></a></h3>
+<p>If the pull request should trigger the GitHub workflow for the ontology repository to run QC checks, follow the following steps:</p>
+<ol class="arabic simple">
+<li><p>Go to the <cite>Settings</cite> tab =&gt; <cite>Secrets and variables</cite> =&gt; <cite>Actions</cite> and add a new repository secret with the name <cite>GH_TOKEN</cite> and the value of the personal access token.
+For more information on personal access tokens, see <a class="reference external" href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#personal-access-tokens-classic">here</a>.</p></li>
+<li><p>The <code class="docutils literal notranslate"><span class="pre">token:</span> <span class="pre">${{</span> <span class="pre">secrets.GH_TOKEN</span> <span class="pre">}}</span></code> in the workflow file should be uncommented.</p></li>
+</ol>
 </section>
 </section>
 </section>