Add github actions for build verification and releases.

Author: NicholasMTElliott

.gitattributes

@@ -0,0 +1 @@
+*.sh text eol=lf

.github/workflows/build.yml

@@ -0,0 +1,33 @@
+name: Build and Test
+
+on:
+  push:
+    branches: [ '**' ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Fetch all history for tags and branches
+      
+      - name: Setup .NET
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: '9.0.x'
+      
+      - name: Fix line endings and run build script
+        run: |
+          sed -i 's/\r$//' ./build_check_release.sh
+          chmod +x ./build_check_release.sh
+          ./build_check_release.sh
+      
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: check-release-builds
+          path: check_release_dist/
+          retention-days: 7

.github/workflows/release.yml

@@ -0,0 +1,54 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - 'release/v*.*.*'
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Fetch all history for tags and branches
+      
+      - name: Extract version from tag
+        id: get_version
+        run: echo "VERSION=$(echo ${GITHUB_REF#refs/tags/release/v})" >> $GITHUB_OUTPUT
+      
+      - name: Update version in project file
+        run: |
+          VERSION=${{ steps.get_version.outputs.VERSION }}
+          sed -i "s/<Version>.*<\/Version>/<Version>$VERSION<\/Version>/g" CheckRelease.csproj
+          # If Version tag doesn't exist, add it
+          if ! grep -q "<Version>" CheckRelease.csproj; then
+            sed -i "/<PropertyGroup>/a \    <Version>$VERSION<\/Version>" CheckRelease.csproj
+          fi
+      
+      - name: Setup .NET
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: '9.0.x'
+      
+      - name: Fix line endings and build release
+        run: |
+          sed -i 's/\r$//' ./build_check_release.sh
+          chmod +x ./build_check_release.sh
+          ./build_check_release.sh
+      
+      - name: Create Release
+        id: create_release
+        uses: softprops/action-gh-release@v1
+        with:
+          name: Release v${{ steps.get_version.outputs.VERSION }}
+          draft: false
+          prerelease: false
+          files: |
+            check_release_dist/win-x64/check_release.win-x64.exe
+            check_release_dist/win-arm64/check_release.win-arm64.exe
+            check_release_dist/linux-x64/check_release.linux-x64
+            check_release_dist/linux-arm64/check_release.linux-arm64
+            check_release_dist/osx-x64/check_release.osx-x64
+            check_release_dist/osx-arm64/check_release.osx-arm64
+          generate_release_notes: true

.gitignore

@@ -2,4 +2,5 @@ publish/
 obj/
 bin/
 check_release_dist/
-.vs/
+.vs/
+memory-bank/

CONTRIBUTING.md

@@ -69,7 +69,28 @@ We welcome suggestions for new features or improvements:
 - Update documentation as needed
 - Add a clear description of your changes
 
-## Versioning Guidelines
+### Continuous Integration
+
+All pull requests are automatically built and tested using GitHub Actions. The following checks will run:
+
+1. **Build and Test**: Runs the `build_check_release.sh` script to:
+   - Execute all tests
+   - Build the application for all supported architectures
+   - Ensure everything compiles correctly
+
+Pull requests cannot be merged until all checks pass. This helps maintain code quality and ensures that changes don't break existing functionality.
+
+### Branch Protection
+
+The main branch is protected with the following rules:
+
+1. Pull requests must be reviewed and approved before merging
+2. The "Build and Test" workflow must pass before merging
+3. Direct pushes to the main branch are not allowed
+
+These protections help ensure that only high-quality, tested code is merged into the main branch.
+
+## Versioning and Release Guidelines
 
 This project follows [Semantic Versioning (SEMVER)](https://semver.org/). When contributing, please indicate the type of change:
 
@@ -88,6 +109,8 @@ This project follows [Semantic Versioning (SEMVER)](https://semver.org/). When c
 - Performance improvements
 - Documentation updates
 
+For detailed information about the release process, please see [RELEASING.md](docs/RELEASING.md).
+
 ## Coding Standards
 
 We value clean, readable code but don't want to burden contributors with overly strict guidelines. Here are some basic principles:

CheckRelease.csproj

@@ -8,6 +8,7 @@
     <PublishTrimmed>true</PublishTrimmed>
     <TrimMode>link</TrimMode>
     <SuppressTrimAnalysisWarnings>false</SuppressTrimAnalysisWarnings>
+    <Version>1.0.0</Version>
   </PropertyGroup>
 
   <ItemGroup>

README.md

@@ -3,6 +3,8 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![.NET](https://img.shields.io/badge/.NET-9.0-512BD4)](https://dotnet.microsoft.com/download/dotnet/9.0)
 [![Version](https://img.shields.io/badge/Version-1.0.0-blue)](https://github.com/SkywardApps/check-release/releases)
+[![Build Status](https://github.com/SkywardApps/check-release/actions/workflows/build.yml/badge.svg)](https://github.com/SkywardApps/check-release/actions/workflows/build.yml)
+[![Release Status](https://github.com/SkywardApps/check-release/actions/workflows/release.yml/badge.svg)](https://github.com/SkywardApps/check-release/actions/workflows/release.yml)
 
 A C# tool for analyzing and displaying changes between Git tags with JIRA ticket extraction and Slack unfurling support.