Update GitHub Actions workflow to use PAT_TOKEN for releases

Author: benjavides

.github/workflows/build-and-release.yml

@@ -72,7 +72,7 @@ jobs:
     - name: Create Release
       uses: actions/create-release@v1
       env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
       with:
         tag_name: v${{ steps.get_version.outputs.version }}
         release_name: Release v${{ steps.get_version.outputs.version }}
@@ -94,7 +94,7 @@ jobs:
     - name: Upload Release Asset
       uses: actions/upload-release-asset@v1
       env:
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        GITHUB_TOKEN: ${{ secrets.PAT_TOKEN }}
       with:
         upload_url: ${{ steps.create_release.outputs.upload_url }}
         asset_path: ./dist/UE-Git-Plugin-Manager.exe

docs/AUTOMATED_RELEASES.md

@@ -0,0 +1,78 @@
+# Automated Releases
+
+This project uses GitHub Actions to automatically build and release new versions when changes are pushed to the main branch.
+
+## How it works
+
+1. **Trigger**: Every push to the `main` branch triggers the build and release workflow
+2. **Version Control**: The version is controlled by the `VERSION` file in the repository
+3. **Building**: The application is built using the same process as `build.bat`
+4. **Release**: A new GitHub release is created with the built executable using the version from the VERSION file
+
+## Version Management
+
+- The version is stored in the `VERSION` file (e.g., `1.0.2`)
+- **Developer controls the version**: Update the VERSION file to the desired version before pushing
+- Version format follows semantic versioning: `MAJOR.MINOR.PATCH`
+- The workflow uses whatever version is specified in the VERSION file
+
+### Version Update Process
+
+**Before creating a release:**
+1. Update the `VERSION` file to the desired version (e.g., `1.0.2`)
+2. Commit and push your changes to the main branch
+3. The GitHub Action will automatically create a release with that version
+
+**Example workflow:**
+```bash
+# Update VERSION file to 1.0.2
+echo "1.0.2" > VERSION
+
+# Commit and push
+git add VERSION
+git commit -m "Prepare release v1.0.2"
+git push origin main
+
+# GitHub Action automatically creates release v1.0.2
+```
+
+## Manual Release
+
+You can also trigger a release manually:
+1. Go to the "Actions" tab in GitHub
+2. Select "Build and Release" workflow
+3. Click "Run workflow" button
+4. Choose the branch (usually `main`) and click "Run workflow"
+
+## Release Assets
+
+Each release includes:
+- `UE-Git-Plugin-Manager.exe` - The built executable ready to run
+
+## Workflow Details
+
+The GitHub Action workflow (`/.github/workflows/build-and-release.yml`) performs these steps:
+
+1. **Setup**: Checkout code, setup Go 1.21
+2. **Version Reading**: Read version from VERSION file
+3. **Build Process**: 
+   - Create necessary directories (`logs`, `dist`)
+   - Download dependencies (`go mod tidy`)
+   - Build executable (`go build -o dist/UE-Git-Plugin-Manager.exe .`)
+   - Verify the executable was created
+4. **Release Creation**: Create GitHub release with the version from VERSION file
+5. **Asset Upload**: Upload the built executable as a release asset
+
+## Requirements
+
+- Go 1.21 or later
+- Windows build environment (GitHub Actions provides this)
+- Proper Git permissions for the repository
+
+## Troubleshooting
+
+If the workflow fails:
+1. Check the Actions tab for error details
+2. Ensure the `VERSION` file exists and contains a valid version number
+3. Verify that the Go build process works locally with `build.bat`
+4. Check that all dependencies are properly specified in `go.mod`

manage_version.bat

@@ -0,0 +1,89 @@
+@echo off
+echo UE Git Plugin Manager - Version Management
+echo.
+
+REM Check if VERSION file exists
+if not exist "VERSION" (
+    echo VERSION file not found! Creating with default version...
+    echo 1.0.1 > VERSION
+    echo Created VERSION file with version 1.0.1
+    echo.
+)
+
+REM Read current version
+set /p CURRENT_VERSION=<VERSION
+echo Current version: %CURRENT_VERSION%
+
+echo.
+echo Options:
+echo 1. Show current version
+echo 2. Set patch version (e.g., 1.0.2)
+echo 3. Set minor version (e.g., 1.1.0)
+echo 4. Set major version (e.g., 2.0.0)
+echo 5. Set custom version
+echo 6. Exit
+echo.
+
+set /p choice="Enter your choice (1-6): "
+
+if "%choice%"=="1" goto show_version
+if "%choice%"=="2" goto set_patch
+if "%choice%"=="3" goto set_minor
+if "%choice%"=="4" goto set_major
+if "%choice%"=="5" goto set_custom
+if "%choice%"=="6" goto exit
+goto invalid_choice
+
+:show_version
+echo Current version: %CURRENT_VERSION%
+goto end
+
+:set_patch
+for /f "tokens=1,2,3 delims=." %%a in ("%CURRENT_VERSION%") do (
+    set /a NEW_PATCH=%%c+1
+    set NEW_VERSION=%%a.%%b.!NEW_PATCH!
+)
+echo %NEW_VERSION% > VERSION
+echo Version set to: !NEW_VERSION!
+goto end
+
+:set_minor
+for /f "tokens=1,2,3 delims=." %%a in ("%CURRENT_VERSION%") do (
+    set /a NEW_MINOR=%%b+1
+    set NEW_VERSION=%%a.!NEW_MINOR!.0
+)
+echo %NEW_VERSION% > VERSION
+echo Version set to: !NEW_VERSION!
+goto end
+
+:set_major
+for /f "tokens=1,2,3 delims=." %%a in ("%CURRENT_VERSION%") do (
+    set /a NEW_MAJOR=%%a+1
+    set NEW_VERSION=!NEW_MAJOR!.0.0
+)
+echo %NEW_VERSION% > VERSION
+echo Version set to: !NEW_VERSION!
+goto end
+
+:set_custom
+set /p NEW_VERSION="Enter new version (e.g., 1.2.3): "
+echo %NEW_VERSION% > VERSION
+echo Version set to: %NEW_VERSION%
+goto end
+
+:invalid_choice
+echo Invalid choice. Please enter 1-6.
+goto end
+
+:end
+echo.
+echo Next steps:
+echo 1. Commit this change: git add VERSION
+echo 2. Commit: git commit -m "Prepare release v%NEW_VERSION%"
+echo 3. Push: git push origin main
+echo 4. GitHub Action will automatically create the release
+echo.
+pause
+goto exit
+
+:exit