Page MenuHomePhabricator

When triggering audits, respect committer identities when importing commits
ClosedPublic

Authored by epriestley on Jun 17 2019, 5:04 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 9:54 PM
Unknown Object (File)
Fri, Dec 13, 5:58 AM
Unknown Object (File)
Wed, Dec 11, 6:59 AM
Unknown Object (File)
Wed, Dec 11, 6:59 AM
Unknown Object (File)
Wed, Dec 11, 6:40 AM
Unknown Object (File)
Wed, Dec 11, 5:26 AM
Unknown Object (File)
Mon, Dec 2, 7:31 AM
Unknown Object (File)
Sat, Nov 30, 1:07 AM
Subscribers
None

Details

Summary

Ref T13311. We currently don't use committer identity mappings when triggering audits, so if a user is only associated with an identity via manual mapping we won't treat them as the author.

Instead, use the identity and manual mapping if they're available.

Test Plan
  • Pushed a commit as xyz <xyz@example.org>, an address with no corresponding user.
  • In the UI, manually associated that identity with user @alice.
  • Ran bin/repository reparse --publish <hash> to trigger audits and publishing for the commit.
  • Before: observed the $author_phid was null.
  • After: observed the $author_phid is Alice.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable