You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-25Lines changed: 0 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,31 +13,6 @@ While this is inspired by that project, this does not contain any actual code fr
13
13
14
14
when this is done I will submit this to winget!!
15
15
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:
0 commit comments