diff --git a/site/index.html b/site/index.html index 0f7eb72..278293e 100644 --- a/site/index.html +++ b/site/index.html @@ -3,19 +3,88 @@ - team-ai-sync - Sync AI guidance across every repo + Sync AI Files Across Repos | team-ai-sync + + + + + + + +
@@ -57,13 +126,29 @@
-

Open-source CI/CD automation

-

Keep every repo aligned with your team's AI guidance

+

Open-source repo file sync for AI teams

+

Sync AI guidance files across repositories

- Sync `AGENTS.md`, `CLAUDE.md`, prompts, editor settings, and shared - repository conventions from one source of truth into every target - repo through normal pull requests or merge requests. + team-ai-sync copies files such as AGENTS.md, + CLAUDE.md, prompts, editor settings, and repository + rules from one source repo to many target repos. It does not merge + directly. It opens pull requests or merge requests so each team can + review the change.

+
+
+ You maintain one source repo. + Put the files every project should share in one place. +
+
+ CI runs team-ai-sync. + The tool validates config, copies files, and creates a branch. +
+
+ Targets get PRs or MRs. + Repository owners review and merge the generated updates. +
+

Keep every repo aligned with your team's AI guidance

- One source of truth - Centralize guidance once instead of copy-pasting it per repo. + Problem it solves + Stop manually copying AI instructions and prompt files across many repos.
- Review-first rollout - Every target receives a normal PR or MR for local ownership. + Best fit + Platform, DevEx, and engineering teams that manage many service repos.
- Native CI/CD packaging - Use the package that matches where your repositories live. + Result + Consistent agent guidance, prompts, and repo rules with reviewable changes.

How it works

-

Sync shared assets without bypassing repo review

+

One config file controls what gets copied and where it goes

- The source repository owns `sync-config.json` and the files your team - wants to standardize. A CI workflow runs `team-ai-sync`, clones each - target, copies configured files, pushes a sync branch, and opens or - updates one review request per changed repository. + The source repository owns sync-config.json and the + shared files your team wants to standardize. A CI workflow runs + team-ai-sync, clones each target, copies configured + files, pushes a sync branch, and opens or updates one review + request per changed repository.

    @@ -226,7 +312,7 @@

    Use the native package for each CI/CD ecosystem

     @@ -257,7 +343,7 @@

    GitLab CI/CD Component

    Bitbucket Pipe

    - Call `paladini/team-ai-sync:1.0.0` from Bitbucket Pipelines and + Call paladini/team-ai-sync:1.0.0 from Bitbucket Pipelines and provide username and API token variables with repository access.

    Read Bitbucket setup @@ -274,10 +360,11 @@

    Bitbucket Pipe

    What to sync

    -

    Share the files that make AI-assisted work consistent

    +

    Sync the files developers look for before using AI in a repo

    - Keep instructions, prompts, review guidance, and editor defaults - aligned across API, web, infrastructure, and service repositories. + Keep coding-agent instructions, prompt templates, review guidance, + editor defaults, and repository conventions aligned across API, + web, infrastructure, and service repositories.

    @@ -333,7 +420,7 @@

    Open real PRs or MRs

    See the full lifecycle in public repos

    The demo shows dry-run validation, PR creation, PR updates, merge, - and a final no-change run with `changed=false`. + and a final no-change run with changed=false.

    @@ -357,7 +444,7 @@

    Everything needed for production rollout

    Configuration reference - Understand every `sync-config.json` field and default. + Understand every sync-config.json field and default. Authentication @@ -383,7 +470,7 @@

    Everything needed for production rollout

    Safe by default

    Designed for reviewable repository operations

    - `team-ai-sync` does not merge generated PRs or MRs, bypass branch + team-ai-sync does not merge generated PRs or MRs, bypass branch protection, manage secrets, or change repository settings. It validates paths, rejects traversal, and keeps target maintainers in the approval loop. @@ -392,7 +479,7 @@

    Designed for reviewable repository operations

    Path safety - Rejects absolute paths, `..`, `.git`, and paths outside repo roots. + Rejects absolute paths, .., .git, and paths outside repo roots.
    Dry-run mode @@ -404,6 +491,41 @@

    Designed for reviewable repository operations

    + +
    +
    +

    Questions developers ask

    +

    Plain answers before you install it

    +
    +
    +
    + What does team-ai-sync do? +

    + It syncs selected files and directories from one source + repository to multiple target repositories. Instead of changing + target default branches directly, it creates or updates PRs and + MRs. +

    +
    +
    + Why would a developer team use it? +

    + Use it when many repos need the same AGENTS.md, + CLAUDE.md, prompts, code review rules, editor + settings, or AI-agent instructions, and you want updates to stay + reviewable. +

    +
    +
    + Does it work only on GitHub? +

    + No. Use the GitHub Action for GitHub repositories, the GitLab + CI/CD Component for GitLab projects, and the Bitbucket Pipe for + Bitbucket repositories. +

    +
    +
    +