team-ai-sync keeps shared AI collaboration files, prompt files, editor
settings, and repository guidance aligned across multiple repositories through
pull requests or merge requests.
Use this documentation to install the GitHub Action, GitLab CI/CD Component, or Bitbucket Pipe; configure sync rules; create the right token; operate the workflow; and troubleshoot common failures.
- Getting started: create a source repository, configure a workflow, and run your first sync.
- Configuration reference: learn every
sync-config.jsonfield, default value, and behavior. - Authentication and permissions: choose a PAT or GitHub App token and grant the smallest useful permissions.
- Operations guide: run dry runs, update existing pull requests, inspect outputs, and manage repository fleets.
- Platform packages: use the GitHub Action, GitLab CI/CD Component, or Bitbucket Pipe.
- Security model: understand path safety, token handling, pull request boundaries, and safe rollout practices.
- Public demo walkthrough: follow the real public demo repositories, runs, and generated pull requests.
- Troubleshooting: diagnose token, permission, config, branch, label, reviewer, and workflow issues.
- Action repository: paladini/team-ai-sync
- Public source demo: paladini/team-ai-sync-demo-source
- Public API target demo: paladini/team-ai-sync-demo-api
- Public web target demo: paladini/team-ai-sync-demo-web
Use the stable v1 tag in workflows:
- uses: paladini/team-ai-sync@v1
with:
github-token: ${{ secrets.TEAM_SYNC_ADMIN_PAT }}
config-path: sync-config.json