chore: add Quick Start and Release documentation for Windows

Author: keshavbhatt

.github/QUICKSTART.md

@@ -0,0 +1,105 @@
+# Quick Start: Releasing TorrHunt on Windows
+
+## One-Command Release
+
+```bash
+# Update version, commit, tag, and push
+VERSION="1.0.0"
+git add .
+git commit -m "Release v${VERSION}"
+git tag -a v${VERSION} -m "Release version ${VERSION}"
+git push origin main v${VERSION}
+```
+
+## What Happens Next?
+
+1. **GitHub Actions starts automatically** (watch at: Actions tab)
+2. **~10-15 minutes later**: Windows executables are ready
+3. **Release page updated** with:
+   - Installer (recommended)
+   - Portable ZIP
+   - Checksums for verification
+   - Auto-generated release notes
+
+## Testing the Workflow
+
+Want to test without creating a real release?
+
+```bash
+# Create a test tag
+git tag -a v0.0.1-test -m "Test release"
+git push origin v0.0.1-test
+
+# Delete test release and tag later from GitHub UI
+```
+
+## Requirements
+
+✅ GitHub repository  
+✅ Actions enabled (free for public repos)  
+✅ Tag format: `v*.*.*` (e.g., v1.0.0)  
+❌ No secrets or tokens needed  
+
+## Workflow Features
+
+- ✅ Builds with Qt 6.4.2
+- ✅ Creates Windows installer (Inno Setup)
+- ✅ Creates portable ZIP
+- ✅ Includes all dependencies
+- ✅ SHA256 checksums
+- ✅ Auto-generated release notes
+- ✅ Artifacts retained for 30 days
+
+## Customization
+
+Edit `.github/workflows/release.yml` to:
+- Change Qt version
+- Modify installer settings
+- Add/remove files
+- Change release description
+- Add multiple platforms (Linux, macOS)
+
+## Example Workflow
+
+```bash
+# 1. Make changes
+vim src/main.cpp
+
+# 2. Test locally
+cd src && qmake && make
+
+# 3. Commit changes
+git add .
+git commit -m "Add new feature"
+
+# 4. Release
+git tag v1.1.0 -m "Version 1.1.0 - Added new feature"
+git push origin main v1.1.0
+
+# 5. Wait ~15 minutes
+# 6. Check: https://github.com/YOUR_USERNAME/torrhunt/releases
+```
+
+## Troubleshooting
+
+**Build failed?**
+- Check Actions log
+- Verify Qt version compatibility
+- Check .pro file syntax
+
+**Release not created?**
+- Ensure tag format is `v*.*.*`
+- Check GITHUB_TOKEN permissions
+- Verify Actions are enabled
+
+**Missing files in release?**
+- Check windeployqt output
+- Verify file paths in workflow
+- Add missing resources to copy step
+
+## Support
+
+- Workflow issues: Check `.github/workflows/release.yml`
+- Build errors: Review Actions logs
+- Qt issues: Verify version in workflow matches your development environment
+

.github/RELEASE.md

@@ -0,0 +1,69 @@
+# Creating a Release
+
+This project uses GitHub Actions to automatically build and release Windows executables.
+
+## How to Create a Release
+
+1. **Update Version**: Make sure the version is updated in your project files (e.g., `src/untitled.pro` or version headers)
+
+2. **Commit Changes**: Commit all your changes
+   ```bash
+   git add .
+   git commit -m "Release v1.0.0"
+   ```
+
+3. **Create and Push Tag**: Create a version tag following semantic versioning
+   ```bash
+   git tag -a v1.0.0 -m "Release version 1.0.0"
+   git push origin v1.0.0
+   ```
+
+4. **Automatic Build**: GitHub Actions will automatically:
+   - Build the Windows 64-bit executable
+   - Create an installer (.exe)
+   - Create a portable ZIP package
+   - Generate checksums
+   - Create a GitHub Release with all artifacts
+
+## Version Tag Format
+
+Use semantic versioning: `v<major>.<minor>.<patch>`
+- `v1.0.0` - Major release
+- `v1.1.0` - Minor update (new features)
+- `v1.0.1` - Patch release (bug fixes)
+
+## Release Artifacts
+
+Each release will include:
+- **Installer**: `TorrHunt-Setup-v1.0.0-Win64.exe` - Full installer with shortcuts
+- **Portable**: `TorrHunt-Portable-v1.0.0-Win64.zip` - Extract and run anywhere
+- **Checksums**: `checksums.txt` - SHA256 hashes for verification
+
+## Monitoring the Build
+
+After pushing a tag, you can monitor the build progress at:
+`https://github.com/<your-username>/torrhunt/actions`
+
+## Manual Release
+
+If you need to manually create a release without the workflow:
+1. Go to the repository's Releases page
+2. Click "Draft a new release"
+3. Create a new tag or select an existing one
+4. Fill in the release notes
+5. Upload pre-built binaries
+6. Publish the release
+
+## Troubleshooting
+
+- **Build fails**: Check the Actions log for detailed error messages
+- **Missing dependencies**: The workflow installs Qt 6.4.2 automatically
+- **Tag not triggering build**: Ensure tag follows `v*.*.*` format
+
+## Requirements
+
+The workflow requires:
+- GitHub repository with Actions enabled
+- No additional secrets needed (uses `GITHUB_TOKEN` automatically)
+- Windows runner (provided by GitHub)
+