After branching and deploying a new feature in an integration environment, a developer confirms it is working correctly. They now need to deploy these changes to the parent 'staging' environment…

Question

Options

• A'magento-cloud environment:deploy'
• B'magento-cloud environment:push'
• C'magento-cloud environment:merge'
• D'magento-cloud git:merge'

• A
  4% (1)
• B
  9% (2)
• C
  87% (20)

Explanation

magento-cloud environment:merge is the dedicated CLI command for merging a child environment's code up into its parent, which is exactly what's needed here - it handles the integration-to-staging promotion cleanly and triggers a redeployment on the parent. Option A (environment:deploy) redeploys the current environment but does not move code to the parent. Option B (environment:push) pushes local git changes to a remote environment but does not perform a parent merge. Option D (git:merge) is not a valid magento-cloud CLI subcommand - the tool uses environment: as its namespace for branch/environment operations, not git:. Memory tip: Think of it as "merging up the environment tree" - the word merge maps directly to the action, and environment: is the correct namespace for all branch-lifecycle commands in the Magento Cloud CLI.

No community discussion yet for this question.