From 95fffa8928f083adcd84080fa03c667bde36b43f Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 21:34:25 +0800
Subject: [PATCH 1/8] test so i can compile without doing anything on my pc

---
 .github/workflows/cmake-single-platform.yml | 39 +++++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 .github/workflows/cmake-single-platform.yml

diff --git a/.github/workflows/cmake-single-platform.yml b/.github/workflows/cmake-single-platform.yml
new file mode 100644
index 00000000..4bd1c79b
--- /dev/null
+++ b/.github/workflows/cmake-single-platform.yml
@@ -0,0 +1,39 @@
+# This starter workflow is for a CMake project running on a single platform. There is a different starter workflow if you need cross-platform coverage.
+# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-multi-platform.yml
+name: CMake on a single platform
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+env:
+  # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
+  BUILD_TYPE: Release
+
+jobs:
+  build:
+    # The CMake configure and build commands are platform agnostic and should work equally well on Windows or Mac.
+    # You can convert this to a matrix build if you need cross-platform coverage.
+    # See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Configure CMake
+      # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
+      # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
+      run: cmake -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=${{env.BUILD_TYPE}}
+
+    - name: Build
+      # Build your program with the given configuration
+      run: cmake --build ${{github.workspace}}/build --config ${{env.BUILD_TYPE}}
+
+    - name: Test
+      working-directory: ${{github.workspace}}/build
+      # Execute tests defined by the CMake configuration.
+      # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
+      run: ctest -C ${{env.BUILD_TYPE}}
+

From e21ed8d40ea06db36ebb95e8ee1671302069b6f3 Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 21:36:54 +0800
Subject: [PATCH 2/8] Delete .github/workflows/cmake-single-platform.yml

didnt work
---
 .github/workflows/cmake-single-platform.yml | 39 ---------------------
 1 file changed, 39 deletions(-)
 delete mode 100644 .github/workflows/cmake-single-platform.yml

diff --git a/.github/workflows/cmake-single-platform.yml b/.github/workflows/cmake-single-platform.yml
deleted file mode 100644
index 4bd1c79b..00000000
--- a/.github/workflows/cmake-single-platform.yml
+++ /dev/null
@@ -1,39 +0,0 @@
-# This starter workflow is for a CMake project running on a single platform. There is a different starter workflow if you need cross-platform coverage.
-# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-multi-platform.yml
-name: CMake on a single platform
-
-on:
-  push:
-    branches: [ "master" ]
-  pull_request:
-    branches: [ "master" ]
-
-env:
-  # Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
-  BUILD_TYPE: Release
-
-jobs:
-  build:
-    # The CMake configure and build commands are platform agnostic and should work equally well on Windows or Mac.
-    # You can convert this to a matrix build if you need cross-platform coverage.
-    # See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
-    runs-on: ubuntu-latest
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Configure CMake
-      # Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
-      # See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
-      run: cmake -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=${{env.BUILD_TYPE}}
-
-    - name: Build
-      # Build your program with the given configuration
-      run: cmake --build ${{github.workspace}}/build --config ${{env.BUILD_TYPE}}
-
-    - name: Test
-      working-directory: ${{github.workspace}}/build
-      # Execute tests defined by the CMake configuration.
-      # See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
-      run: ctest -C ${{env.BUILD_TYPE}}
-

From 13e12060df8382acf5cc28e8e3be9d80bd92eed7 Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 21:38:57 +0800
Subject: [PATCH 3/8] Create msbuild.yml

---
 .github/workflows/msbuild.yml | 44 +++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 .github/workflows/msbuild.yml

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/msbuild.yml
new file mode 100644
index 00000000..921f09eb
--- /dev/null
+++ b/.github/workflows/msbuild.yml
@@ -0,0 +1,44 @@
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: MSBuild
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+
+env:
+  # Path to the solution file relative to the root of the project.
+  SOLUTION_FILE_PATH: .
+
+  # Configuration type to build.
+  # You can convert this to a build matrix if you need coverage of multiple configuration types.
+  # https://docs.github.com/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
+  BUILD_CONFIGURATION: Release
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: windows-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Add MSBuild to PATH
+      uses: microsoft/setup-msbuild@v1.0.2
+
+    - name: Restore NuGet packages
+      working-directory: ${{env.GITHUB_WORKSPACE}}
+      run: nuget restore ${{env.SOLUTION_FILE_PATH}}
+
+    - name: Build
+      working-directory: ${{env.GITHUB_WORKSPACE}}
+      # Add additional options to the MSBuild command line here (like platform or verbosity level).
+      # See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
+      run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}

From ec0a60fa461708d0dc819a874abea1d1e07cb53e Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 21:52:42 +0800
Subject: [PATCH 4/8] Update msbuild.yml

---
 .github/workflows/msbuild.yml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/msbuild.yml
index 921f09eb..e60434b6 100644
--- a/.github/workflows/msbuild.yml
+++ b/.github/workflows/msbuild.yml
@@ -42,3 +42,7 @@ jobs:
       # Add additional options to the MSBuild command line here (like platform or verbosity level).
       # See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
       run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
+      
+    - name: Find those damn dlls
+      working-directory: ${{env.GITHUB_WORKSPACE}}
+      run: dir /s /p "*.dll"

From 6a0e219a26b818784c43193eb93efc3ea3fdf6d2 Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 21:58:15 +0800
Subject: [PATCH 5/8] Update msbuild.yml

---
 .github/workflows/msbuild.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/msbuild.yml
index e60434b6..8f1b13ea 100644
--- a/.github/workflows/msbuild.yml
+++ b/.github/workflows/msbuild.yml
@@ -45,4 +45,4 @@ jobs:
       
     - name: Find those damn dlls
       working-directory: ${{env.GITHUB_WORKSPACE}}
-      run: dir /s /p "*.dll"
+      run: Get-ChildItem -Path . -Recurse -Filter "*.dll"

From d5517d13ee9969142afe264fefe99654f366203b Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 22:03:25 +0800
Subject: [PATCH 6/8] Update msbuild.yml

---
 .github/workflows/msbuild.yml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/msbuild.yml
index 8f1b13ea..ff4206ab 100644
--- a/.github/workflows/msbuild.yml
+++ b/.github/workflows/msbuild.yml
@@ -43,6 +43,8 @@ jobs:
       # See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
       run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
       
-    - name: Find those damn dlls
-      working-directory: ${{env.GITHUB_WORKSPACE}}
-      run: Get-ChildItem -Path . -Recurse -Filter "*.dll"
+    - name: Upload Release DLL to artifacts
+      uses: actions/upload-artifacts@v4
+      with:
+        name: Latite-Release
+        path: D:\a\Latite\Latite\x64\Release\LatiteRewrite.dll

From a996b70d409c39ede54f6a2595cd50f8e4c7818d Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 22:04:16 +0800
Subject: [PATCH 7/8] Update msbuild.yml

---
 .github/workflows/msbuild.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/msbuild.yml
index ff4206ab..568b35eb 100644
--- a/.github/workflows/msbuild.yml
+++ b/.github/workflows/msbuild.yml
@@ -44,7 +44,7 @@ jobs:
       run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
       
     - name: Upload Release DLL to artifacts
-      uses: actions/upload-artifacts@v4
+      uses: actions/upload-artifact@v4
       with:
         name: Latite-Release
         path: D:\a\Latite\Latite\x64\Release\LatiteRewrite.dll

From c483fd890b373fee7f982182a92a155055d74ee9 Mon Sep 17 00:00:00 2001
From: Raspberry <84133368+EpiclyRaspberry@users.noreply.github.com>
Date: Sat, 24 Aug 2024 22:44:49 +0800
Subject: [PATCH 8/8] Workflow to build latite from source every push/merge

tnx gemini for help
---
 .../workflows/{msbuild.yml => releasebuild.yml}    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
 rename .github/workflows/{msbuild.yml => releasebuild.yml} (81%)

diff --git a/.github/workflows/msbuild.yml b/.github/workflows/releasebuild.yml
similarity index 81%
rename from .github/workflows/msbuild.yml
rename to .github/workflows/releasebuild.yml
index 568b35eb..f7d7344a 100644
--- a/.github/workflows/msbuild.yml
+++ b/.github/workflows/releasebuild.yml
@@ -2,8 +2,7 @@
 # They are provided by a third-party and are governed by
 # separate terms of service, privacy policy, and support
 # documentation.
-
-name: MSBuild
+name: Build Latite from source
 
 on:
   push:
@@ -33,17 +32,18 @@ jobs:
     - name: Add MSBuild to PATH
       uses: microsoft/setup-msbuild@v1.0.2
 
-    - name: Restore NuGet packages
-      working-directory: ${{env.GITHUB_WORKSPACE}}
-      run: nuget restore ${{env.SOLUTION_FILE_PATH}}
+    # - name: Restore NuGet packages
+    #   working-directory: ${{env.GITHUB_WORKSPACE}}
+    #   run: nuget restore ${{env.SOLUTION_FILE_PATH}}
+    # apparently this thing isnt really needed
 
-    - name: Build
+    - name: Build Latite
       working-directory: ${{env.GITHUB_WORKSPACE}}
       # Add additional options to the MSBuild command line here (like platform or verbosity level).
       # See https://docs.microsoft.com/visualstudio/msbuild/msbuild-command-line-reference
       run: msbuild /m /p:Configuration=${{env.BUILD_CONFIGURATION}} ${{env.SOLUTION_FILE_PATH}}
       
-    - name: Upload Release DLL to artifacts
+    - name: Upload release DLL to artifacts
       uses: actions/upload-artifact@v4
       with:
         name: Latite-Release