Skip to content

Commit

Permalink
Deploying to gh-pages from @ 9dc0fd8 🚀
Browse files Browse the repository at this point in the history
  • Loading branch information
hrshdhgd committed Mar 18, 2024
1 parent a59338e commit cef0ece
Show file tree
Hide file tree
Showing 3 changed files with 21 additions and 2 deletions.
11 changes: 10 additions & 1 deletion _sources/implementation.rst.txt
Original file line number Diff line number Diff line change
Expand Up @@ -76,4 +76,13 @@ Pull request
Once the issue is created, it triggers the GitHub workflow mentioned above and creates a corresponding pull request
which should reflect the expected change in the ontology resource based on the commands listed in the issue.
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.
the same pull request is updated.

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.
10 changes: 10 additions & 0 deletions implementation.html
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +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>
</ul>
</li>
</ul>
Expand Down Expand Up @@ -165,6 +166,15 @@ <h3>Pull request<a class="headerlink" href="#pull-request" title="Permalink to t
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.</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>
</section>
</section>
</section>

Expand Down
Loading

0 comments on commit cef0ece

Please sign in to comment.