GitHub Actions

While publishing and testing of the library is handled by JetBrains TeamCity, there are some CI operations that are handled by GitHub actions instead.

Publishing Docs

The building of the documentation website in docs, and the publishing of it along with the search-indices is handled by the Build Docs GH Action. Careful: This action replaces the entire contents of the documentation website.

Gradle Wrapper Validation

We run the Gradle Wrapper Validation action using a GitHub Action as well. This action validates the checksums of all Gradle Wrapper JAR files present in the repository and fails if any unknown Gradle Wrapper JAR files are found.

Auto-commit generated code

Anytime the source code changes on master, this GitHub Action makes sure processKDocsMain, and korro are run. If there have been any changes in either core/generated-sources or docs/StardustDocs/snippets, these are auto-committed to the branch, to keep it up to date.

Show generated code in PR

To make sure no unexpected code is auto-committed to master, this GitHub Action runs the same code-generating tasks but on a separate branch. If there are changes, it will leave a message in the PR, informing you about the changes that will be done to the master branch if this PR were merged.