Workflows & Automation

This guide covers practical routines for daily engineering, cross-repository task execution, Git hook automation, and CI/CD integration using Repo Nexus.

Developer Onboarding

Onboarding a new developer onto a multi-repo workspace requires only two commands:

# 1. Clone the meta-repo
git clone git@github.com:my-org/developer-workspace.git
cd developer-workspace

# 2. Clone all member repositories declared in rnex.yaml
rnex clone

All member repositories are automatically cloned into ./repos/, plugins are synchronized, and multi-root workspace files are prepared.

---

Batch Execution with rnex exec

The rnex exec command runs arbitrary shell commands sequentially across every active member repository in ./repos/.

Checking Git Status Across All Repositories

rnex exec git status -s

=== [backend] ===
 M src/api/auth.ts
?? tests/auth_test.ts

=== [frontend] ===
On branch main (working tree clean)

Pulling Latest Changes Everywhere

rnex exec git pull --ff-only

Running Test Suites Sequentially

rnex exec npm test

Exit Code Bubbling

If a command fails in any repository, rnex exec exits immediately with that command's non-zero exit code and displays the failing repository, halting downstream execution unless explicitly handled.

---

Git Hooks Automation

Repo Nexus includes an automated hook runner configured via core.hooksPath = .rnex/hooks.

Core Automated Hooks

1. post-merge: When you pull updates to the meta-repo (git pull), the hook automatically executes rnex fix to:
   • Clone newly declared member repositories.
   • Update AI routing instructions (AGENTS.md, etc.).
   • Sync plugin changes.
2. Plugin Triggers: Plugins can subscribe to hook events (e.g. karpathy-llm running wiki consistency checks on merge).

Managing Hooks

# Check current hook status
rnex hooks status

# Reinstall or repair hooks
rnex hooks install

# Uninstall hooks and restore git default
rnex hooks uninstall

---

CI/CD Integration

Repo Nexus integrates cleanly into GitHub Actions, GitLab CI, or CircleCI pipelines.

Example: Running Cross-Repo Lints in GitHub Actions

name: Workspace Lint

on:
  pull_request:
    branches: [ main ]

jobs:
  lint-all:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout Meta-Repo
        uses: actions/checkout@v4

      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 22

      - name: Install Repo Nexus
        run: npm install -g repo-nexus

      - name: Clone Shallow Repositories
        run: rnex clone

      - name: Run Linters Across All Repos
        run: rnex exec npm run lint