.github/workflows/game_ci.yml

@@ -1,7 +1,7 @@
-name: "Godot 4.2.1 CI/CD"
+name: "Godot 4.1.2 CI/CD"
 
 env:
-  GODOT_VERSION: 4.2.1
+  GODOT_VERSION: 4.1.2
 
 on:
   workflow_dispatch:
@@ -15,7 +15,7 @@ jobs:
     permissions:
       contents: write
     container:
-      image: barichello/godot-ci:4.2.1
+      image: barichello/godot-ci:4.1.2
     steps:
       - name: Checkout
         uses: actions/checkout@v3
@@ -60,7 +60,7 @@ jobs:
       contents: write
 
     container:
-      image: barichello/godot-ci:4.2.1
+      image: barichello/godot-ci:4.1.2
 
     steps:
       - name: Checkout
@@ -90,7 +90,7 @@ jobs:
       contents: write
 
     container:
-      image: barichello/godot-ci:4.2.1
+      image: barichello/godot-ci:4.1.2
 
     steps:
       - name: Checkout
@@ -166,7 +166,7 @@ jobs:
           body: |
             Release notes for ${{env.GitVersion_MajorMinorPatch}}
           draft: false
-          prerelease: true
+          prerelease: false
 
       - name: Upload Web Release Asset
         id: upload-release-asset

README.md

@@ -1,23 +1,16 @@
 # Overview
-This is a repository that provides a template for you to start your Godot repositories on GitHub. This repository contains a basic project setup along with CI/CD. By default it will build for windows, linux and the web and upload their artifacts, along with deploying a build to GitHubDock Pages.
-
-# Docker Image
-This uses a open source docker image made for exporting from godot, it can be found here.
-https://github.com/abarichello/godot-ci
-
+This is a repository that provides a template for you to start your Godot repositories on GitHub. This repository contains a basic project setup along with CI/CD. By default it will build for windows, linux and the web and upload their artifacts, along with deploying a build to GitHub Pages.
 # How to deploy to GitHub Pages
 Go to the settings of your repository, and then on the left hand side click pages. You should then be able to click a drop down near the top of the page to deploy from a branch, deploy from the gh-pages branch once the workflow has executed.
-Example Deployment https://D4M13N-D3V.github.io/godot_template/
+Example Deployment https://damientehdemon.github.io/godot_template/
 ![image](https://github.com/DamienTehDemon/godot_template/assets/13697702/80a76d39-65be-4de4-ab47-91fbeb3eabd2)
 
-# Changing the Godot version
-You can do this by making a small change to the workflow file in `/.github/workflows/game_ci.yaml`. At the top of the file you will see a environment variable for the godot version, just change this to whatever version you want to use to build your game. By default this is 4.2 right now.
 # Recommended Flow
-To use this properly we recommend creating pull requests into the main branch, and merging your changes in that way. This is to prevent using all of your action runner quota. We recommend making a small change to the workflow file in `/.github/workflows/game_ci.yaml` and changing line `169` from `prerelease: false` to `prerelease: true`. Whenever you want to do a proper release, you can go to the list of releases on your repository and change it to be a full release instead of pre-release. This will allow you to have builds for every version of the game, while also maintaining a selection of stable builds.
+To use this properly we recommend creating pull requests into the main branch, and merging your changes in that way. We recommend making a small change to the workflow file in `/.github/workflows/game_ci.yaml` and changing line `169` from `prerelease: false` to `prerelease: true`. Whenever you want to do a proper release, you can go to the list of releases on your repository and change it to be a full release instead of pre-release. This will allow you to have builds for every version of the game, while also maintaining a selection of stable builds.
 # Requirments
 In order for the workflows in this repository to work with an existing project it requires certain export profiles to be configured. You need to have a windows, linux, and web export configured using the default names: "Windows Desktop","Linux/X11", and "Web".
 # Migrating existing project
-If you want to add this to an existing GitHub repository, just copy and paste the `.github` folder into the root of your existing repository, along with the `export_presets.cfg` file. As long as your project has these exports and resides in the root of the repository the GitHub workflows should work fine. 
+If you want to add this to an existing GitHub repository, just copy and paste the `.github` folder into the root of your existing repository. As long as your project has these exports and resides in the root of the repository the GitHub workflows should work fine. 
 # Versioning
 When you push to the `main` branch the workflow will automatically be executed. The workflow will build for Web,Linux, and Windows, and then upload the build artifacts to the workflow. Then a new step will execute which will generate version numbers based on the commits. You can see below which keywords a commit message must start with to increment a major,minor, or patch number. At the end the workflow will create a release and upload the build artifacts to it.