- prevent creating new release if the same release already exist
- prevent creating new release if there are uncommitted file modifications
- checking of the mod "VERSION" keyword, prevent creating '2.1.3' release when you mod version is '2.1.2'
- release description can be edited before creating new release
- initial release description is generated from commit messages between two latest tags
Windows 10 - Git
Windows 7/8.1 - Git, .NET Framework 4.5.2 or above and Powershell 5.1/Powershell 6
macOS - Git and Powershell 6
Linux - Git and Powershell 6
-
Download and extract this repository, move everything from 'ModRelease-master' folder directly into the folder where you keep all other top-level mod folders.
-
Open https://github.com/settings/tokens, and create "personal access token" with "public_repo" privilege, it's not you password, you can revoke it at any time, more info: https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line.
-
Save it to "#ModRelease-Github-Key-Example.txt" file and rename it to #ModRelease-Github-Key.txt
-
Put #ModRelease.bat inside mod top-level directory, use the included mod example as reference.
-
Increase mod version inside mod file.
-
Create new commit. Do not create new tag for release, it will be created automatically from mod version and pushed into online repository.
optional step: create mod packages (release assets), wait until all packages are created with proper names:
ModID-version.exe ModID-version.iemod ModID-version.zip
-
Run #ModRelease.bat and follow further instructions.