@@ -5,11 +5,11 @@ documentation from a local repository to GitHub Pages.
55
66## Usage
77
8- To use this workflow developers must have a ` requirements.txt ` file to define
9- the sphinx dependencies that will be used by the ` build-sphinx-docs ` workflow.
10- By default the workflow will look for a ` requirements.txt ` file in the top
11- level of the calling project repository. An example of a ` requirements.txt `
12- file which could run this workflow would be as follows:
8+ To use this workflow developers must have a ` requirements.txt ` file to define
9+ the sphinx dependencies that will be used by the ` build-sphinx-docs ` workflow.
10+ By default the workflow will look for a ` requirements.txt ` file in the top level
11+ of the calling project repository. An example of a ` requirements.txt ` file which
12+ could run this workflow would be as follows:
1313
1414### Example requirements
1515
@@ -53,9 +53,10 @@ Here the user would implement this file and replace each of the parameters with
5353the respective data types as dictated by the inputs section of the
5454` build-sphinx-docs.yaml` file.
5555
56- Following the calling of the `build-sphinx-docs` workflow, the `deploy-sphinx-docs`
57- workflow can be used to deploy the generated html documentation to the GitHub
58- webserver. This workflow can be called from a workflow using the form describe below :
56+ Following the calling of the `build-sphinx-docs` workflow, the
57+ ` deploy-sphinx-docs` workflow can be used to deploy the generated html
58+ documentation to the GitHub webserver. This workflow can be called from a
59+ workflow using the form describe below :
5960
6061# ## Deploy built HTML to GitHub Pages
6162
@@ -69,10 +70,10 @@ steps:
6970 timeout: Timeout for the job in minutes (5)
7071` ` `
7172
72- Both of these steps can be combined to produce a simple build and deploy documentation
73- pipeline for a repository :
73+ Both of these steps can be combined to produce a simple build and deploy
74+ documentation pipeline for a repository :
7475
75- # ## Example continuous intergration pipeline in an external repository
76+ # ## Example continuous integration pipeline in an external repository
7677
7778An example workflow to build Sphinx documentation and deploy it to GitHub Pages
7879when changes are pushed to the `main` branch :
9293 requirements: /path/to/requirements.txt
9394 runner: ubuntu-24.04
9495 timeout: 10
95- docs-directory: ' /path/to/documentation'
96- sphinx-opts: ' extra options'
97- build-directory: ' /path/to/build/html'
96+ docs-directory: " /path/to/documentation"
97+ sphinx-opts: " extra options"
98+ build-directory: " /path/to/build/html"
9899
99100 deploy-docs:
100101 if: github.ref == 'refs/heads/main'
0 commit comments