-
Notifications
You must be signed in to change notification settings - Fork 433
Open
Labels
type: featurecode contributing to the implementation of a feature and/or user facing functionalitycode contributing to the implementation of a feature and/or user facing functionality
Description
Which problem is this feature request solving?
Currently my CI/CD uses the netlify CLI to push built artifacts into a draft deploy or a production deploy; currently, production is indicated by a specific git branch , e.g. if "deploy" is built it pushes to prod, or if any other branch is built it pushes to a draft deploy with the branch name in the deploy name. I realized I would like better control over this process without having to maintain a special branch.
Describe the solution you'd like
This could be fixed by adding a command line option to netlify deploy to promote a previous draft deploy to prod. It could either be a wholly separate subcommand e.g. netlify deploy promote --from= DEPLOY_ID_OR_ALIAS, or it could be an option to netlify deploy --prod, e.g. netlify deploy --prod --from=DEPLOY_ID_OR_ALIAS.
Pull request (optional)
- I can submit a pull request.
Metadata
Metadata
Assignees
Labels
type: featurecode contributing to the implementation of a feature and/or user facing functionalitycode contributing to the implementation of a feature and/or user facing functionality