sync-ag-shared

Orchestrates ag-shared subrepo push/pull sync across AG repos with PRs.

1|1|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/ag-grid/ag-shared --skill sync-ag-shared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-ag-shared
Source: https://github.com/ag-grid/ag-shared/tree/main/prompts/skills/sync-ag-shared
Command: npx skills add https://github.com/ag-grid/ag-shared --skill sync-ag-shared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates centralized syncing of external/ag-shared subrepo changes from the current repo to all AG repos that consume it, coordinating git subrepo push/pull cycles, companion changes, and cross-referenced PRs.

Core Features & Use Cases

  • Orchestrates end-to-end subrepo synchronization across ag-charts, ag-grid, and ag-studio whenever ag-shared changes.
  • Generates and applies companion changes across destinations (rules, prompts, scripts) to maintain consistency.
  • Use Case: when updating ag-shared in a feature branch, run this skill to push updates and create synchronized PRs across all dependent repos.

Quick Start

Run this skill on a feature branch to push ag-shared updates and sync them across destination repositories.

Frequently Asked Questions about sync-ag-shared

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

FAQPage Schema
How do I sync a git subrepo across multiple repositories?

To sync a git subrepo across multiple repositories, you can orchestrate subrepo push and pull cycles from a feature branch to push updates and create synchronized PRs across all dependent destination repos.

What is the best way to manage cross-repo PRs for a shared subrepo?

Managing cross-repo PRs for a shared subrepo requires orchestrating push and pull cycles alongside companion changes to coordinate destination repos and generate synchronized, cross-referenced pull requests.

How do I apply companion changes across multiple repos when updating a shared dependency?

Applying companion changes across multiple repos involves orchestrating subrepo synchronization to automatically generate and apply updates to rules, prompts, and scripts in destination repositories for consistency.

Do I need a clean working tree to run a multi-repo subrepo sync?

Yes, a multi-repo subrepo sync requires a clean working tree, a valid external subrepo .gitrepo file in the source repo, and Git, gh, and yarn installed to validate and proceed.

Can I run a subrepo sync from any git worktree directory?

No, the subrepo sync must be invoked from the source worktree directory where the feature branch exists, allowing destination repositories to be detected dynamically during validation.

Why does my multi-repo subrepo push fail during synchronization?

A multi-repo subrepo push may fail during synchronization if the working tree is not clean, the external subrepo .gitrepo file is missing, or Git, gh, and yarn dependencies are not properly installed.