This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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).
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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
Currently, when creating a personal access token in the Watson Studio "Gitlab Self-Managed" integration (checked as of WS 10.0.0, CP4D 5.1), it's not possible to specifiy a git user email, only a user name. Instead, the email in the main CP4D account is used. When none is specified there, "noreply@ibm.com" is used. This is not communicated anywhere and needs to be inferred from the commits created when using the git integration.
Especially when the git instance is configured to reject pushes by unknown users as a security feature, as is possible in Gitlab using its "Push rules" feature, specifically settings like "check whether the commit author is a gitlab author" - this is problematic. Scenarios where different emails are have to be used for Gitlab and CP4D authentication are also not covered. In our case, we happen to use the same email adresses for both, but this is not necessarily the case.
We would need an additional, optional field for the gitlab user email in the form and for this email to be used as git config mail throughout the integration. This would increase transparency, avoid issues with the push rules and decouple the emails that should be unrelated anyway.
Needed By | Quarter |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.