Skip to content

Commit e74b1c4

Browse files
fix: improve PR file detection and revert README changes
Co-authored-by: supervoidcoder <88671013+supervoidcoder@users.noreply.github.com>
1 parent 0f33994 commit e74b1c4

2 files changed

Lines changed: 2 additions & 26 deletions

File tree

.github/workflows/release.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ jobs:
2424
shell: pwsh
2525
run: |
2626
# Get list of changed files in the merged PR
27-
$changedFiles = git diff --name-only HEAD~1 HEAD
27+
$changedFiles = git diff --name-only ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }}
2828
Write-Output "Changed files:"
2929
Write-Output $changedFiles
3030
@@ -177,6 +177,7 @@ jobs:
177177
} else {
178178
Write-Output "Compilation failed with exit code: $exitCode"
179179
Write-Output "compile_success=false" >> $env:GITHUB_OUTPUT
180+
Write-Error "Build failed - release will be skipped"
180181
exit 1
181182
}
182183

README.md

Lines changed: 0 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -13,31 +13,6 @@ While this is inspired by that project, this does not contain any actual code fr
1313

1414
when this is done I will submit this to winget!!
1515

16-
## Automatic Releases
17-
18-
This project uses GitHub Actions to automatically compile and release new versions when PRs are merged to the main branch.
19-
20-
**How it works:**
21-
- Releases are triggered when a PR is merged to `main` (not on every push)
22-
- Only releases if C++ source files (`.cpp`, `.h`, `.hpp`, etc.) were changed
23-
- README-only changes or other non-code changes won't trigger a release
24-
- The build must compile successfully before creating a release
25-
- If compilation fails, no release is created
26-
- The release version is automatically incremented at the patch level (e.g., v0.1.0 → v0.1.1, v0.0.5 → v0.0.6)
27-
- Release notes are generated from commit messages
28-
- If you use [conventional commits](https://www.conventionalcommits.org/) (e.g., `fix: bug description`, `feat: new feature`), the release notes will be nicely formatted with emojis
29-
- Otherwise, the commit message is used as-is
30-
- The compiled binary (`win-witr.exe`) is attached to each release
31-
- Only patch versions are auto-released; major (1.0, 2.0) and minor (0.1, 0.2) releases are done manually
32-
33-
**Compilation flags:**
34-
The automatic builds use Microsoft's C++ compiler (MSVC) with:
35-
- `/O2` - Maximum optimization for speed
36-
- `/Ot` - Favor fast code
37-
- `/GL` - Whole program optimization
38-
- `/DUNICODE` and `/D_UNICODE` - Unicode support
39-
- `/std:c++20` - C++20 standard
40-
4116
**Why C++?**
4217

4318
- I don't know crap about Go

0 commit comments

Comments
 (0)