How to set up custom Greenworks Prebuilds using Travis CLI

Requirements

• GitHub Desktop Software
• Notepad++ Software
• Travis CLI Account

1. Preparing Files

1. GitHub Fork Prebuilds (Keep the name!)
2. GitHub Fork Greenworks (Any name!)
3. Clone your Prebuilds Fork locally using GitHub Desktop
4. Switch to the master branch if required
5. Open the .travis.yml file using Notepad++
6. Edit line 63 and replace the URL with your custom Greenworks Fork URL
   (Example: - git clone https://github.com/TheRealDannyyy/Steam4C2-Custom-Prebuilds greenworks)
7. Open the following files in Notepad++:

• gh.js [greenworks-prebuilds\utils]
• Readme.md [greenworks-prebuilds]
• Package.json [greenworks-prebuilds]

9. For each file in Notepad++:
   Search > Replace... > Find what: "electronforconstruct" > Replace with: #Your Account Name# (e.g. TheRealDannyyy) > Replace All
10. Save changes for each file (.travis.yml; gh.js; Readme.md; Package.json)
11. OPTIONAL: Update Steamworks files inside the SDK.zip, if required by your custom Greenworks Fork

2. Preparing Travis CLI

1. Activate GitHub Apps Integration for Travis CLI
2. Select your GitHub Greenworks Prebuilds Fork Repository
3. Navigate to: More Options... > Settings... > Environment Variables
4. Generate a new token on GitHub with the name GH_TOKEN
5. Copy the given token value (optional: back it up it inside a local text file)
6. Add new Environment Variable on Travis CLI with the name GH_TOKEN and the given token as the value
7. Add another Environment Variable with the name ZIP_PASSWORD and the requested password as a value

3. Pushing Travis CLI Builds

1. Go to GitHub desktop and commit + push the file changes
2. Travis CLI will now build your prebuilds (check under "build history" tab for your repository)
3. Cancel build process by pressing the "X" in the build "history history" tab
4. Navigate to: More Options... > Settings... > Cron Jobs
5. Select your branch, interval and always run (this will automatically build files)