New environments placed under production when pushed from Git

Last update: November 6, 2024

CREATED FOR:

  • Developer

This article provides a solution for the issue where new environments are placed under the production environment on Adobe Commerce on cloud infrastructure when pushed from the git version-control system.

Affected products and versions

Issue

Prerequisites:

Have a local git controlled clone of the project.

Steps to reproduce:

You need to create an integration branch from the staging branch:

  1. Switch to the staging branch by running the following command in the local shell: git checkout staging
  2. Create an integration branch from the staging branch by running the following command in the local shell: git checkout -b <branch>
  3. Push the branch to the remote repository and set up an upstream branch by running the following command in the local shell: git push --set-upstream origin <branch>

Expected results:

The new branch is created under the staging branch.

Actual results:

The new branch was created under the production branch.

Cause

This is not a bug. For setting a parent branch for another branch, the merchant should use the magento-cloud CLI.

Solution

A parent branch can only be set after the merchant has pushed a newly created branch and activated it. Refer to Adobe Commerce on cloud infrastructure > Bitbucket integration in our developer documentation.

To update a parent for the existing branch on the server, please use the magento-cloud environment:info command in the magento-cloud CLI.

Example of usage:

magento-cloud environment:info parent Staging

This will set the parent branch to “Staging” for the currently checked out branch.