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)
Sun, Feb 2, 5:27 AM
Unknown Object (File)
Thu, Jan 30, 3:06 AM
Unknown Object (File)
Wed, Jan 29, 3:41 PM
Unknown Object (File)
Tue, Jan 28, 5:17 AM
Unknown Object (File)
Mon, Jan 27, 7:31 AM
Unknown Object (File)
Sat, Jan 25, 5:15 AM
Unknown Object (File)
Sat, Jan 25, 5:15 AM
Unknown Object (File)
Sat, Jan 25, 5:15 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