Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
Rust
docs: point CONTRIBUTING and the PR template at release/3.3
Vinícius DS Andradee9efa00f0d4d
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.mdindex 20e510c4..86a76d31 100644--- a/.github/pull_request_template.md+++ b/.github/pull_request_template.md@@ -32,7 +32,7 @@breaking MCP schema change, called out in "What changed" above- [ ] The base branch matches: `main` for a patch, the standing feature- branch (currently `release/3.2`) for minor or major work.+ branch (currently `release/3.3`) for minor or major work.- [ ] I checked that this does not redo something already on `main` or thefeature branch, or fixed by a closed issue.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 462eb475..53f729e9 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -196,9 +196,9 @@ than the following major release.- **Pick the base branch from that impact.** A fix targets `main`. A newcapability (flag, subcommand, MCP tool, config key, agent harness,provider, companion) targets the standing feature branch, currently- `release/3.2`. A fix to code that exists only on the feature branch+ `release/3.3`. A fix to code that exists only on the feature branchtargets that branch too.- **Check what already landed first.** Before opening a PR, look for the- issue's closing commit and search `git log origin/main origin/release/3.2`+ issue's closing commit and search `git log origin/main origin/release/3.3`for the feature or fix. A closed issue usually means the work shipped;a PR that redoes it gets closed, however good it is.