What
The setup-ci command / initCi() already supports 5 CI providers internally (GitHub Actions, GitLab CI, CircleCI, Bitbucket, Azure DevOps) but there's no CLI flag to select one. Auto-detection works, but users can't override.
Add a --ci-provider flag:
$ mcp-observatory setup-ci --all --ci-provider gitlab-ci
$ mcp-observatory setup-ci --all --ci-provider circleci
$ mcp-observatory setup-ci --all --ci-provider bitbucket-pipelines
$ mcp-observatory setup-ci --all --ci-provider azure-pipelines
Files
src/commands/init-ci.ts — the InitCiOptions interface already has ciProvider, just need to add the CLI option and wire it through the command registration.
Acceptance
What
The
setup-cicommand /initCi()already supports 5 CI providers internally (GitHub Actions, GitLab CI, CircleCI, Bitbucket, Azure DevOps) but there's no CLI flag to select one. Auto-detection works, but users can't override.Add a
--ci-providerflag:Files
src/commands/init-ci.ts— theInitCiOptionsinterface already hasciProvider, just need to add the CLI option and wire it through the command registration.Acceptance
--ci-providerflag accepts: github-actions, gitlab-ci, circleci, bitbucket-pipelines, azure-pipelines