From 132065a8bc57c557fd406b048b9a275eafc1a8a9 Mon Sep 17 00:00:00 2001
From: Oded Falik <oded@odeds-mbp.lan>
Date: Tue, 13 Jan 2026 09:46:22 -0800
Subject: [PATCH] docs: add contributing guide with release workflow

---
 CONTRIBUTING.md | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 CONTRIBUTING.md

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..337059b
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,37 @@
+# Contributing to Lambda CLI
+
+## Development
+
+```bash
+git clone https://github.com/Strand-AI/lambda-cli.git
+cd lambda-cli
+cargo build
+cargo test
+```
+
+## Pull Requests
+
+1. Fork the repo and create a branch
+2. Make your changes
+3. Run `cargo fmt` and `cargo clippy`
+4. Open a PR against `main`
+
+## Releasing
+
+Releases are automated via PR labels. To create a release:
+
+1. Open a PR with your changes
+2. Add one of these labels:
+   - `release:patch` - Bug fixes (0.2.0 → 0.2.1)
+   - `release:minor` - New features (0.2.0 → 0.3.0)
+   - `release:major` - Breaking changes (0.2.0 → 1.0.0)
+3. Merge the PR
+
+When merged, CI will automatically:
+- Bump the version in `Cargo.toml`
+- Create a git tag
+- Build binaries for Linux and macOS
+- Create a GitHub release
+- Update the Homebrew formula
+
+No label = no release. PRs without release labels are regular code changes.