Guides > Configuration
Sync your monorepos
# Sync your monorepos import VideoEmbed from '@components/VideoEmbed.astro'; import { Steps } from '@astrojs/starlight/components'; Learn how to use Derp’s Rules system to connect interrelated repositories and automate type updates across your stack. <VideoEmbed url="https://youtu.be/bndY6opaA7w?si=6zZWh4aB8f8kCD5F" title="Syncing monorepos for agent context video" /> --- ## Intro This tutorial teaches you how to define **global Rules** in Derp so your coding agent understands how your projects relate to one another. By linking monorepos (e.g., server, client, and shared API schemas), Derp automatically updates types and schemas across repos when you make a change in one place. Although this example uses Derp’s internal repos, the same workflow applies to any multi-repo setup. --- ## The problem When projects are split into multiple repos — like backend, client, and shared schema — developers often forget to synchronize type changes manually. That’s error-prone and time-consuming. Derp solves this by teaching your **agent** the relationships between your repos through a global Rule. --- ## The Rule setup Describe each repository and its connection to the others. ### Example Rule ``` We have three inter-related projects in ~/Repos: derp-internal (client-side application) derp-server (server application) derp-proto-apis (shared API schemas for each) When you update the schema types, push to git and update the installed types in the server and client by the commit hash. ``` Once defined, Derp automatically follows these instructions when a schema file is changed. <Steps> 1. #### When the schema updates — update server types `cd` into the server repository and run the appropriate commands to regenerate/update server-side types based on the changed schema. 2. #### When the schema updates — update client types `cd` into the client repository and run the appropriate commands to regenerate/update client-side types so the client stays in sync with the schema changes. </Steps> --- :::tip Benefits * Keeps your **schema, server, and client** perfectly in sync * Reduces merge conflicts and version drift * Saves manual steps when committing or deploying :::Define global Rules in Derp to keep monorepo schemas, server types, and client types automatically synchronized across repositories.
Learn how to use Derp’s Rules system to connect interrelated repositories and automate type updates across your stack.
This tutorial teaches you how to define global Rules in Derp so your coding agent understands how your projects relate to one another.
By linking monorepos (e.g., server, client, and shared API schemas), Derp automatically updates types and schemas across repos when you make a change in one place.
Although this example uses Derp’s internal repos, the same workflow applies to any multi-repo setup.
The problem
Section titled “The problem”When projects are split into multiple repos — like backend, client, and shared schema — developers often forget to synchronize type changes manually.
That’s error-prone and time-consuming. Derp solves this by teaching your agent the relationships between your repos through a global Rule.
The Rule setup
Section titled “The Rule setup”Describe each repository and its connection to the others.
Example Rule
Section titled “Example Rule”We have three inter-related projects in ~/Repos:
derp-internal (client-side application)
derp-server (server application)
derp-proto-apis (shared API schemas for each)
When you update the schema types, push to git and update the installed types in the server and client by the commit hash.Once defined, Derp automatically follows these instructions when a schema file is changed.
-
When the schema updates — update server types
Section titled “When the schema updates — update server types”cdinto the server repository and run the appropriate commands to regenerate/update server-side types based on the changed schema. -
When the schema updates — update client types
Section titled “When the schema updates — update client types”cdinto the client repository and run the appropriate commands to regenerate/update client-side types so the client stays in sync with the schema changes.