Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Mar 16, 2023

Set Branch name with a property on a Git Source Component

For a Git Source Component or Component Template, it would be great to set the branch name of the repository depending on some property. I would like to change the branch depending on the environment. Now I have the same component replicated for every environment. 

Then I could set a diferent status to every component version depending on this same property, and define environment gates to block deploys to some environments depending on the component version status.

Idea priority Low
  • Guest
    Mar 16, 2023

    I'll try with an example.

    We have a component to deploy something from a git source. We deploy to produccion from master, buy to integration from a develop brach, or from a release branch. I could reuse the component setting the branch depending on a environment property.

    1. Developer make a change and commit to a release branch. A new component version is created to deploy this change to the integration environment.

    2. If everything goes right, the release branch merges to master. Then a diferent component creates a new version from master branch in order to deploy to production.

    I want to reuse the component and create environment related versions, with a status or version name convention. A environment gate can allow or block deploys to an environment for a determined version.

    Today we are working with a component for every source branch.

    3 replies
  • Admin
    Osman Burucu
    Mar 16, 2023

    Please could you provide more details what you want to achieve? Use cases, mock-ups and more description will help us to understand the request.

    Thank You in advance