[wbogusz-poolside]

Why

We want CI in git-backed skill repositories to kick Console syncs directly after a commit lands, without requiring teams to wire their own curl scripts. This gives repositories a supported action that can either target a known Console repository ID or discover matching Console repositories from the GitHub remote.

What

• Added action-repo-sync/action.yml, a composite GitHub Action for syncing Console repositories via POST /v0/repositories/{id}/sync
• Supports explicit repository_id or auto-discovery through GET /v0/repositories by matching normalized GitHub remotes against https://github.com/${{ github.repository }}
• Falls back to per-repository GET /v0/repositories/{id} when list summaries do not include remote_url, preserving compatibility with older Console deployments
• Sends commit_sha in the sync payload, defaulting to the workflow commit SHA when the input is omitted
• Treats reused sync responses as successful and skips polling when Console reports the commit is already synced
• Polls latest_version_info until the requested version is ready, errors, times out, or is superseded by a newer sync
• Emits a comma-separated version_ids output for all repositories synced or reused by the action
• Added action-repo-sync/README.md with inputs, outputs, explicit-ID and auto-discovery examples, token provisioning guidance, and troubleshooting notes

[wbogusz-poolside]

Closing — relocated to the forge monorepo per repo-scoping discussion: this action calls the repositories/data-sources API, not Bridge's surface, and centralized Poolside infra lives in forge. Successor: poolsideai/forge#44313. Consumer updated: poolsideai/poolside-skills#35.