Cross Repo Dev

Step 1: Identify Scope

Determine which repos need changes and the dependency order:

1. dash-react first (if UI components change)
2. dash-core second (if framework changes)
3. dash-electron last (consuming app)

If only one dependency repo changes, skip the others.

Step 2: Make Changes in Dependency Repo

# In the dependency repo (dash-core or dash-react)
cd ~/Development/<repo>/<repo>
git checkout -b feat/<description>

# Make code changes...

# Run local CI to validate
npm run ci

Step 3: Link and Test in dash-electron

Linking dash-core

cd ~/Development/dash-electron/dash-electron
npm run link-core -- ~/Development/dash-core/dash-core
rm -rf node_modules/.cache
npm run dev
# Ask user to verify changes work

Linking dash-react

cd ~/Development/dash-electron/dash-electron
npm run link-react -- ~/Development/dash-react/dash-react
rm -rf node_modules/.cache
npm run dev
# Ask user to verify changes work

Run dash-electron CI

cd ~/Development/dash-electron/dash-electron
npm run ci

Step 4: Unlink and Ship

Unlink

cd ~/Development/dash-electron/dash-electron
npm run unlink-core   # or npm run unlink-react

Ship the dependency repo

cd ~/Development/<dependency-repo>/<dependency-repo>

# Option A: Create PR for review
npm run ci:pr -- -m "description of changes"

# Option B: Full release (merge + tag)
npm run ci:release -- -m "description of changes"

Wait for auto-publish, then update dash-electron

After the dependency repo's PR is merged and the package is published:

cd ~/Development/dash-electron/dash-electron
# Update the version in package.json
npm install
npm run ci

Step 5: Jira Transitions

Move the ticket through statuses at the right moments:

mcp__claude_ai_Atlassian__transitionJiraIssue({
  cloudId: "7b4552a1-0fb9-4194-b92f-ded50fefa326",
  issueIdOrKey: "DASH-X",
  transition: { id: "<transition-id>" }
})

CI Commands (All Repos)

Each flag is cumulative -- --release runs all prior steps.

npm run ci                          # validate only
npm run ci:commit -- -m "message"   # validate + commit + bump
npm run ci:push -- -m "message"     # above + push
npm run ci:pr -- -m "message"       # above + create PR
npm run ci:release -- -m "message"  # above + merge + tag + cleanup

Multi-Repo Change Checklist

• Changes made in dependency repo
• npm run ci passes in dependency repo
• Linked into dash-electron and tested
• npm run ci passes in dash-electron (while linked)
• Unlinked from dash-electron
• Dependency repo PR created/merged
• dash-electron updated to published version
• npm run ci passes in dash-electron (with published version)
• Jira ticket transitioned appropriately