This is an IBM Automation portal for Integration 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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
I think the point here is that you need to use another software (whether GUI or CLI git client) in order to commit and push your changes to a repository for CI/CD processes to kick in, whereas what would be expected here is that there's built-in git client functionality in Designer that allows for that OOTB. Most IDEs I know of have this kind of integrations.
API Connect Designer (desktop installed tool) works with files on the filesystem which can be synced folders with a source control system. All of the development that I personally do with API Connect Designer is against files that are then synced using Github Desktop back to my public or internal enterprise repos. The same project folders have assets that I use with other development tools based on my project scope (e.g. VSCode, WebStorm, XCode). By interacting with the filesystem you are not limited to a specific source control system or waiting on updated plugin with our local graphical developer tooling.
Outside of not being able to interact with the source control system directly from our graphical editor all of the capabilities as described are already able to be accomplished.
We will leave the ticket open for 60 days for additional details, clarifications, or feedback. Thanks.