Clarify CI/CD deploy environment selection in zuplo-cli skill#9
Merged
Conversation
Explain that `zuplo deploy` selects the environment from the current git branch (default branch maps to production), so `--environment` should be left unset in normal CI/CD. Document when to set it explicitly (no git repo, or deliberate named-environment/tag deploys) and note the default branch is configurable in the portal. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the zuplo-cli skill documentation to clarify how zuplo deploy selects the target Zuplo environment in CI/CD, emphasizing the default branch-based environment mapping and positioning --environment as an exception.
Changes:
- Rewrote the
zuplo deploycommand reference to describe branch→environment mapping (default branch → production) as the default behavior. - Updated “Deploy from CI/CD” guidance to remove the hardcoded
--environment production, add a branch-based deployment example, and document when--environmentshould be used.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Improves the
zuplo-cliskill's guidance on how agents should set up CI/CD deployments.The previous "Deploy from CI/CD" example hardcoded
--environment production, which is misleading. In CI/CD you typically should not set--environment— the CLI reads the current git branch and maps it to the matching Zuplo environment automatically (the default branch, usuallymain, maps to the production environment).Changes (
skills/zuplo-cli/SKILL.md)--environment productionwith the correct branch-based flow (npx zuplo deploy --account my-account --project my-project), explained the branch→environment mapping, noted the default branch is configurable in the portal, and documented when--environmentis needed (no git repo, or deliberate named-environment/tag deploys such as staging→production).zuplo deploycommand reference: reworded so branch-based environment selection is the default and--environmentis presented as the exception.🤖 Generated with Claude Code