garamatic-multirepo

Coordinate multi-repo contract updates across Garamatic services with validation and rollback guardrails.

Updated Dec 11, 2024

Search Tags:#workflow #devops #orchestration #contracts #multirepo #garamatic

Ready to run

npx skills add https://github.com/huaxel/dotfiles --skill garamatic-multirepo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: garamatic-multirepo
Source: https://github.com/huaxel/dotfiles/tree/main/skills/garamatic-multirepo
Command: npx skills add https://github.com/huaxel/dotfiles --skill garamatic-multirepo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates multi-repo changes across Garamatic microservices to ensure consistency and reduce manual drift.

Core Features & Use Cases

Cross-repo coordination: propagate shared contracts from integration-contracts to dependent services.
Parallel updates: orchestrate worktrees and per-service tasks to minimize downtime.
Use Case: When a shared contract changes, update integration-contracts, then apply updates across ticket-masala, mailing-service, event-planner, garamatic-web, and masala-web.

Quick Start

Run the garamatic-multirepo skill to synchronize contract updates across all Garamatic services.

Frequently Asked Questions about garamatic-multirepo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate multi-repo changes across microservices to ensure consistency?▼

Multi-repo changes are coordinated by updating integration-contracts first, then propagating those updates to dependent services like ticket-masala, masala-web, and mailing-service within a defined workflow.

What is the best way to propagate shared contract updates across Garamatic services?▼

Propagating shared contract updates starts by applying changes to integration-contracts, then orchestrating parallel updates to ticket-masala, mailing-service, event-planner, garamatic-web, and masala-web.

How do I manage parallel updates with per-repo worktrees for microservices?▼

Parallel updates are managed by orchestrating per-repo worktrees and per-service tasks, enforcing requirements for tagged states to minimize downtime and reduce manual drift across repositories.

Can I rollback multi-repo changes if a contract update fails across services?▼

Rollback guardrails are enforced during multi-repo changes, providing clear validation and allowing you to safely revert contract updates propagated across dependent Garamatic services.

When do I need to use a multi-repo orchestration workflow for contract changes?▼

A multi-repo orchestration workflow is needed when a shared contract changes and you must apply synchronized updates across integration-contracts and dependent services to prevent manual drift.

Does Garamatic multirepo require tagged states before applying service updates?▼

Tagged states are required for Garamatic multirepo operations, serving as validation guardrails to safely propagate integration-contracts to dependent services like event-planner and masala-web.