Skip to content

docs(readme): direct users to release tags and document DA/CEA branch model (main-ca) - #292

Open
Harsheet jain (jainharsheet77) wants to merge 1 commit into
microsoft:main-cafrom
jainharsheet77:harsheetjain/readme-releases-guidance-ca
Open

Harsheet jain (jainharsheet77) wants to merge 1 commit into
microsoft:main-cafrom
jainharsheet77:harsheetjain/readme-releases-guidance-ca

Conversation

@jainharsheet77

Copy link
Copy Markdown
Contributor

What & why

Companion to #291 — the identical README change applied to the CEA trunk (main-ca).

Following the new branch/release rulesets and Nkem's feedback, the README should point people to the release tags for each agent flavor instead of cloning a trunk branch directly.

This updates the root README.md:

  • New "Which build to clone (releases, not main)" — clone the latest da-v* (Declarative Agent) or cea-v* (Custom Engine Agent) release tag; check the Releases page for the newest and substitute it.
  • "Get the code" walkthrough step — now clones a release tag, with a no-terminal Source code (zip) fallback, instead of the green < > Code → Download ZIP button.
  • New "Branches and releases" — documents the two-trunk model and where contributions go.

Branch model documented

Branch Trunk for Release line
main Declarative Agent (DA) da-v* (e.g. da-v1.0.0-rc.1)
main-ca Custom Engine Agent (CEA) cea-v* (e.g. cea-v1.0.0-rc.1)

Where contributions go: DA-only → main; CEA-only → main-ca; shared → both main and main-ca.

Both-trunk submission

This is a shared README change submitted to both trunks:

Direct consumers to clone the per-flavor release tag (da-v*/cea-v*) instead of a trunk branch, and add a 'Branches and releases' section explaining main (DA) vs main-ca (CEA) and where contributions go.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
amilandi added a commit that referenced this pull request Sep 23, 2026
The main-ca branch has a repository ruleset that requires four status
checks from ci.yml (Lint Python, Installer script smoke tests,
FlightCheck offline test suite, Product line gate), but ci.yml's
pull_request / push triggers only listed main and release/**. So the
required checks never ran on PRs targeting main-ca, and every PR to
main-ca is stuck in mergeStateStatus=BLOCKED — including #299, #292,
#312, #313 (and no main-ca PR has ever been merged).

Add main-ca to both branch filters so CI runs and unblocks the merge
queue for CEA-taxonomy work.

Co-authored-by: Avery Milandin <amilandin@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 70ddf006-7f8d-48e7-9afa-3fbae73b3864
amilandi added a commit that referenced this pull request Sep 23, 2026
The main-ca branch has a repository ruleset that requires four status
checks from ci.yml (Lint Python, Installer script smoke tests,
FlightCheck offline test suite, Product line gate), but ci.yml's
pull_request / push triggers only listed main and release/**. So the
required checks never ran on PRs targeting main-ca, and every PR to
main-ca is stuck in mergeStateStatus=BLOCKED — including #299, #292,
#312, #313 (and no main-ca PR has ever been merged).

Add main-ca to both branch filters so CI runs and unblocks the merge
queue for CEA-taxonomy work.

Co-authored-by: Avery Milandin <amilandin@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 70ddf006-7f8d-48e7-9afa-3fbae73b3864
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants