Inputs of the Action¶
All paths are relative to the working directory (the repository root), and must be in it.
Input |
Default |
Meaning |
|---|---|---|
|
|
the OMNeT++ project whose NED and MSG files are documented |
|
|
where the site is built |
|
name of the project dir |
name of the project, which titles the NED reference (“<title> NED Reference”) and the C++ API (“<title> C++ Reference”) |
|
the Sphinx project (the directory of |
|
|
|
where the NED reference is generated in the Sphinx project |
|
|
format of the NED reference without Sphinx: |
|
NED source roots of dependencies, |
|
|
documentation of dependencies, as |
|
|
further |
|
|
|
also generate the C++ API |
|
|
source directories for the bundled doxygen configuration |
|
own doxygen configuration instead of the bundled one |
|
|
|
where the C++ API is generated, in the Sphinx project or in the site |
|
|
also build PDFs of the Sphinx project, into the root of the site |
|
further |
|
|
|
fail if |
|
the action’s version |
tag of |
|
image to use instead, as is ( |
|
|
|
upload the site as the GitHub Pages artifact |
Output |
Meaning |
|---|---|
|
absolute path of the built site |
The directories that the action generates (output-dir, and ned-dir and
api-dir in the Sphinx project) are emptied before each build. A directory
that is not empty and was not generated by the action (it has no
.doc-builder file) is not touched: the build fails instead.