Phabricator: How to get the email address of contributors?
bcooksley at kde.org
Tue Jan 2 22:42:08 GMT 2018
On Wed, Jan 3, 2018 at 10:24 AM, Luigi Toscano <luigi.toscano at tiscali.it> wrote:
> Dominik Haumann ha scritto:
>> Hi everyone,
>> it just happened to me again, that I want to commit/push a change of
>> someone else (first-time contributor) with the correct --author="x y
>> <mail...>" data.
>> But Phabricator hides the email address, so I either have to ask via
>> phabricator messages for the email address, which is time consuming,
>> or I simply give up and commit in my own name, claiming work done by
>> Is there a simple way to find out the email address (identity.kde.org
>> does not work, since phab user accounts seem to be separate).
>> Help is very much appreciated. In fact, I would love to simply see the
>> correct email addresses, once I am logged into phabricator. Could that
>> be done?
> Let's restart the discussion where it stopped last time (please read it):
> Phabricator does not hide if the contributor used arcanist to submit the patch.
This is correct. Usage of Arcanist also makes other commit metadata visible.
> IMHO that should work even when git format-patch is used but there is an
> internal disagreement on this.
The only thing needed here are changes to Phabricator to allow it to
extract authorship (and other useful metadata) when dealing with the
output of "git format-patch" and "git show". At the moment changes to
Differential aren't a priority for upstream, but they have indicated
that it is something which is doable so if we submitted a patch it is
quite possible we'd get it integrated.
Much like being able to submit patches using "git push" which is also
on their radar, and which they've also undertaken some of the
technical investigation for.
(Although technically this is much more complicated as you have to
replicate the Git protocol)
> IMHO (more complicated) that should work even with the web submission with
> some checkbox is marked (to publish the email and name), but there is both
> internal disagreement and upstream one on this.
One possible way forward way here would be to utilise a custom field
which can show the necessary authorship information.
We'd have to write the necessary code to do that though.
I believe Wikimedia did something similar to link back to their
central accounts system for user profiles.
More information about the kde-core-devel