Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

chore: establish dev-first integration and CI

tt-a1i72e5ea2e852e
diff --git a/.coderabbit.yaml b/.coderabbit.yaml
index 2fa93dc6..9a8550ee 100644
--- a/.coderabbit.yaml
+++ b/.coderabbit.yaml
@@ -25,6 +25,7 @@ reviews:
suggested_labels: false
suggested_reviewers: false
auto_review:
+ base_branches: ["^dev$"]
enabled: true
drafts: false
auto_incremental_review: true
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index ac999daa..f8318532 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -2,7 +2,7 @@
## Problem and value
-Current-main trigger or rationale, intended outcome, why the approach is worth maintaining, and linked issue/agreed scope:
+Current-base trigger or rationale, intended outcome, why the approach is worth maintaining, and linked issue/agreed scope:
## Stability impact
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 368c2888..d282dfcf 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -2,7 +2,7 @@ name: CI
on:
push:
- branches: [main]
+ branches: [main, dev]
pull_request:
jobs:
diff --git a/.github/workflows/dsh.yml b/.github/workflows/dsh.yml
index bd8ac380..eb66f266 100644
--- a/.github/workflows/dsh.yml
+++ b/.github/workflows/dsh.yml
@@ -8,7 +8,7 @@ on:
- 'scripts/stage-clean-skill.mjs'
- 'scripts/third-party-notices-contract.mjs'
push:
- branches: [main]
+ branches: [main, dev]
paths:
- 'integrations/deepseek-harness/**'
- '.github/workflows/dsh.yml'
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 84585f71..a28747b5 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -14,13 +14,13 @@ Do not include secrets, access tokens, credentials, private repository content,
## Prepare a reviewable change
-Start from the latest `main`. Check whether its existing controls already solve the reported case. Record the comparison base and candidate head.
+Start from the latest `dev` and target `dev` for fixes and features. Check whether its existing controls already solve the reported case. Record the comparison base and candidate head.
Use Draft for unresolved scope or early implementation feedback. At this stage, provide the smallest reproduction and relevant checks. Prepare broad integration evidence and generated artifacts once the approach is settled.
Before requesting final review, explain:
-- The current-main trigger, intended outcome, and why the benefit justifies the implementation and ongoing maintenance cost.
+- The current-base trigger, intended outcome, and why the benefit justifies the implementation and ongoing maintenance cost.
- The changed behavior and shared callers, existing behavior that must remain stable, and any intended compatibility changes.
- The applicable checks, actual results, and reproducible evidence links.
@@ -99,7 +99,9 @@ Treat published versions as immutable. Ordinary feature PRs do not change versio
## Final integration and follow-up
-Refresh `main` and the PR head before final integration; account for relevant base changes and resolve conflicts. Rerun local checks whose evidence was invalidated. Unchanged evidence may be linked with its original revision and reuse rationale; do not relabel it as a new-head run. Verify that required remote CI actually ran on the final head and obey branch protection; zero checks is not green.
+`dev` is the integration and trial-use branch; `main` is the stable branch. Integrate reviewed changes into `dev` first. Promote a tested batch from `dev` to `main` through a separate PR after maintainers have used it on real diagram tasks and confirmed stability. Record the tested revision, usage evidence, and unresolved issues in that PR; passing CI alone does not establish trial-use acceptance. Keep Pages deployment on `main` and formal releases on version tags.
+
+Refresh the target base branch and the PR head before final integration; account for relevant base changes and resolve conflicts. Rerun local checks whose evidence was invalidated. Unchanged evidence may be linked with its original revision and reuse rationale; do not relabel it as a new-head run. Verify that required remote CI actually ran on the final head and obey branch protection; zero checks is not green.
On revision, summarize what changed since the reviewed head and which findings it addresses. This lets reviewers focus on the new diff and outstanding decisions.
diff --git a/REVIEWING.md b/REVIEWING.md
index 128b9041..a1f899eb 100644
--- a/REVIEWING.md
+++ b/REVIEWING.md
@@ -4,7 +4,7 @@ Use this guide for initial and revised PR reviews. Judge the user value, impleme
## Understand the problem and approach
-Record the current main/base and candidate head. Read the linked issue or agreed scope and check the current-main behavior where feasible. Separate the reported problem from the proposed implementation.
+Record the current target base and candidate head. Read the linked issue or agreed scope and check the current-base behavior where feasible. Separate the reported problem from the proposed implementation.
Identify who benefits and whether the approach is worth maintaining. Consider whether existing capabilities or a smaller change would solve the problem. For a new default, schema field, or acceptance policy, clarify the value and compatibility tradeoff early. Reuse decisions already made in the issue or authorized task.
@@ -40,6 +40,6 @@ Assess bot findings against the current diff and existing evidence before forwar
## Re-review and finish
-Compare against the last reviewed head, resolve outstanding findings, and inspect added changes. Check intervening main changes for effects on the earlier assessment. Expand review when those changes invalidate scope or evidence; do not treat an old pass as proof of new behavior.
+Compare against the last reviewed head, resolve outstanding findings, and inspect added changes. Check intervening base changes for effects on the earlier assessment. Expand review when those changes invalidate scope or evidence; do not treat an old pass as proof of new behavior.
Finish when the agreed outcome is delivered, relevant evidence is sufficient, and no acceptance blockers remain. Report non-blocking limitations. A review conclusion does not itself authorize a GitHub approval or merge; follow the authorized action and [final integration requirements](CONTRIBUTING.md#final-integration-and-follow-up).