release ci

[supervoidcoder]

we need a ci that automatically compiles and releases every commit as a 0.0.x version bump with a description of the additions parsed from the commit name
(so if it's fix, say fix and then what's after it, also include the extended description)

only I can release the major releases like 1.0 and minor bumps too like 0.1, the bot will only do 0.1.1 --> 0.1.2 based off releases yknow

[supervoidcoder]

@coderabbitai what do you think doesn't this sound fun?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch details of issue `#13` from the repository
gh issue view 13 --repo supervoidcoder/win-witr --json title,body,number,state,labels,author

Length of output: 549

---

@supervoidcoder Yes, this does sound fun! Automated release pipelines can be really satisfying to set up and watch work. 🚀

Here are some thoughts on your proposal:

What I like:

• Clear separation of concerns: bot handles patch releases, you control major/minor versions
• Automatic release notes from commit messages encourages good commit hygiene
• Every change gets versioned and released, making it easy to track history

Considerations to think about:

1. Quality gates: You might want to only release commits that pass certain checks:

   • All tests passing
   • Builds successfully
   • Maybe even checks on the main/master branch only (not every branch)

2. Version strategy: Consider whether you want:

   • Every commit → new release (could be a lot!)
   • Or every commit to main branch after PR merge
   • Semantic versioning based on commit prefixes (fix: = patch, feat: = minor, BREAKING: = major)

3. Commit message format: You mentioned parsing from commit names. You might want to adopt a convention like:

   • fix: description → patch bump
   • feat: description → minor bump (or keep this manual?)
   • Extended descriptions could come from the commit body

4. Implementation tools: GitHub Actions could handle this with:

   • Semantic release plugins
   • Automatic changelog generation
   • Protected tag patterns to prevent bot from creating major/minor versions

Would you like me to help sketch out a GitHub Actions workflow for this, or do you want to explore the design further first?

[supervoidcoder]

@coderabbitai i know i said no AI in this repo but i really don't care for CI lol github actions workflows I always vibe code them lol

BUT NO AI SHALL TOUCH MY C++ FILE 😠😠😠😠 (only review it)

anyways #14

[supervoidcoder]

@coderabbitai omg bro stop with the plan_code_changes never do that again

[supervoidcoder]

look at the pr

[coderabbitai]

@supervoidcoder Got it! 😅 Sorry about that - I went way overboard with the formal planning stuff. I'll keep it simple and direct from now on. Just let me know what you need, and I'll help without all the ceremony!

For the release workflow, want me to just draft the GitHub Actions YAML directly?

---

✏️ Learnings added

Learnt from: supervoidcoder
URL: https://github.com/supervoidcoder/win-witr/issues/13

Timestamp: 2026-01-16T13:49:20.462Z
Learning: For the win-witr repository (supervoidcoder/win-witr), never use the plan_code_changes feature. The user prefers direct, straightforward responses without formal planning processes.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

[supervoidcoder]

@coderabbitai look at the pr

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch details of PR `#14`
gh pr view 14 --repo supervoidcoder/win-witr --json title,body,number,state,labels,author,files,additions,deletions,changedFiles

# Get the diff to see what changes were made
gh pr diff 14 --repo supervoidcoder/win-witr

Length of output: 9334

---

@supervoidcoder Nice! Copilot agent did a solid job on this one. Here's what I see:

The good stuff:

• ✅ Auto-bumps patch versions only (0.0.x) - exactly what you asked for
• ✅ MSVC flags are all there: /O2 /Ot /GL /DUNICODE /D_UNICODE
• ✅ Parses conventional commits (fix:, feat:, etc.) with emoji formatting 🐛✨
• ✅ Falls back to plain commit message if you don't use conventional format
• ✅ Includes commit body in release notes (capped at 1000 chars so it doesn't go crazy)
• ✅ Proper semantic version sorting so v0.0.10 doesn't come before v0.0.2
• ✅ Nice README documentation explaining how it all works

One tiny thing:
The workflow uses c++20 standard - you might want to verify that's compatible with your code (should be fine, but worth checking).

Otherwise this looks ready to rock! Every push to main will auto-compile and release with notes parsed from your commit messages. You'll still have full control over major/minor releases since it only bumps the patch number.

Want to merge it and give it a spin? 🚀

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: supervoidcoder/win-witr PR: 0
File: :0-0
Timestamp: 2026-01-16T13:49:20.462Z
Learning: For the win-witr repository (supervoidcoder/win-witr), never use the plan_code_changes feature. The user prefers direct, straightforward responses without formal planning processes.