no-docs-only-pr-to-main.mdc
sha256:65ccb454656ea5acdea0a10e559b78bcde1eb6ff753ecc2911bc99d1c3d7cadd
feat(calendar): enforce agent context tiers in retrieval AP…
Human
minor
⚠ breaking
1 day ago
| 1 | --- |
| 2 | description: Avoid docs-only PRs to main; bundle docs with substantive changes |
| 3 | alwaysApply: true |
| 4 | --- |
| 5 | |
| 6 | # No docs-only pull requests to `main` |
| 7 | |
| 8 | **Owner policy (billing):** Do **not** open a GitHub pull request to **`main`** whose **only** changes are under `docs/` (handoffs, parity matrices, playbooks, `AGENT-INTEGRATION.md`, etc.). |
| 9 | |
| 10 | - Ship documentation updates **in the same PR** as the **code, tests, or CI** they belong to (e.g. Track B3 memory wiring + updated `docs/NEXT-SESSION-HOSTED-HUB-MCP.md` together). |
| 11 | - It is fine to **commit** and **`git push`** handoff edits on a **long-lived feature branch** (e.g. `feat/hosted-mcp-prompts-b3`) so work is saved and shareable — just **do not** open a merge-to-`main` PR for docs alone. |
| 12 | - If the user asks only to “update the handoff,” update files on the **current feature branch** and stop; do not create a PR unless they explicitly request a merge that includes non-doc changes. |
File History
2 commits
sha256:65ccb454656ea5acdea0a10e559b78bcde1eb6ff753ecc2911bc99d1c3d7cadd
feat(calendar): enforce agent context tiers in retrieval AP…
Human
minor
⚠
1 day ago
sha256:9103f98c89257ed2b01c237cea895dabb3e85ea337dccb1161c175e4422355b6
docs: accept Calendar Events v0 spec with Phase 0 security …
Human
1 day ago