Add 'commit email' user attribute to the API model for users, ensure it is writeable via the REST API
Release notes
In the Drupal community we provision contributor user accounts in our GitLab instance (git.drupalcode.org) automatically from their Drupal.org user accounts. In the past, we used Drupal.org to manage multiple email accounts per user, and to provide a no-reply 'private' commit email. We would like to migrate multiple email account handling to GitLab, but at the same time we want to be able to bulk set the public commit_email of users to the GitLab provided no-reply address to preserve privacy.
Unfortunately, the user api does not seem to provide the capability to set the commit_email property.
Problem to solve
The problem to solve is providing access to CRUD operations for the 'commit email' attribute of users.
Proposal
The proposal is to add the commit email attribute to the user api: https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/api/users.rb
Before we used GitLab, we had …@….no-reply.drupal.org
addresses with equivalent functionality. We now recommend the GitLab-formatted address for Git config for privacy-conscious people.
The next part of the shift is mass-updating this configuration for everyone. It's ultimately up to everyone to know how Git works locally, but we want to default to privacy for the commits made via our GitLab instance’s UI.
Intended users
The primary persona that needs to use the User API to synchronize 'commit email' data is actually the administrator who integrates GitLab into the business processes of the organization.
That might most closely map to:
Feature Usage Metrics
Frequence of requests for this attribute in the API would be a good way to track usage of this feature.