Skip to content
/ patch-template Public template

Initialize a new Gothic VDF patch right here on GitHub

License

Notifications You must be signed in to change notification settings

szapp/patch-template

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 

Repository files navigation

Patch Template

Coverage

Initialize a new Gothic VDF patch right on here GitHub.

Generating a repository from this template will initialize a new Gothic VDF patch with the necessary file structure based on individual needs. It is helpful to get started with a new patch and ensures everything is setup right from the start with all the necessary checks and build scripts.

Let's get started!

Create a patch

1️⃣ Generate a repository from the template

Do not fork this repository, but generate from template!
Template

2️⃣ In the new repo, open a GitHub issue to initialize the patch

The generated repository's name and its description will serve as the name and description of the patch.

3️⃣ Wait for the initialization to complete

Follow the next steps in the generated issue comments.

Checks and continuous integration

The generated patch repository will be equipped with tests and continuous integration using the following GitHub Actions.

szapp/parsiphae-action

checks the Daedalus syntax on every commit.

szapp/patch-validator

checks the Daedalus symbols and resource file names on every commit.

kirides/vdfsbuilder

builds the patch into a ready to use VDF on every tag and release.

Creating a new tag or publishing a new release will trigger the build action that will create a VDF and attach it to the published release. If Steam Workshop deployment is set up in the build action (.github/workflows/build.yml), the new version will be automatically published to the Steam Workshop.

The build action can also be triggered manually from the Actions menu and will provide the VDF as artifact of the latest commit to download.

Documentation

For details on writing patches, please consult the Ninja documentation.

Troubleshooting

In case the initialization does not start automatically after opening an issue in the generated repository, check the repository settings. Actions and workflows should not be disabled. After enabling them create a new issue and try again.