Change Details

Sometime, the Diffusion commit Feed can show the same author twice. Example: https://we.phorge.it/feed/7252237275361918290/ We could be able to avoid this kind of verbosity: > UsernameFoo committed <commit hash>: <commit msg> (authored by UsernameFoo). If the link to the same author would be shown twice, this could be enough instead: > UsernameFoo committed <commit hash>: <commit msg> The responsible file is probably this one: https://we.phorge.it/source/phorge/browse/master/src/applications/audit/storage/PhabricatorAuditTransaction.php;5e48e16f77fd918607cb943f1b1f78293bb00cee$208-212 | Current | Proposal | |-----------|-----------| | {F342758} | {F342760} |

Sometime, the Diffusion commit Feed can show the same author twice. Example: https://we.phorge.it/feed/7252237275361918290/ We could be able to avoid this kind of verbosity: > UsernameFoo committed <commit hash>: <commit msg> (authored by UsernameFoo). If the link to the same author would be shown twice, this could be enough instead: > UsernameFoo committed <commit hash>: <commit msg> The responsible file is probably this one: https://we.phorge.it/source/phorge/browse/master/src/applications/audit/storage/PhabricatorAuditTransaction.php;5e48e16f77fd918607cb943f1b1f78293bb00cee$208-212 | Current | Proposal | |-----------|-----------| | {F342758} | {F342764} |

Sometime, the Diffusion commit Feed can show the same author twice. Example: https://we.phorge.it/feed/7252237275361918290/ We could be able to avoid this kind of verbosity: > UsernameFoo committed <commit hash>: <commit msg> (authored by UsernameFoo). If the link to the same author would be shown twice, this could be enough instead: > UsernameFoo committed <commit hash>: <commit msg> The responsible file is probably this one: https://we.phorge.it/source/phorge/browse/master/src/applications/audit/storage/PhabricatorAuditTransaction.php;5e48e16f77fd918607cb943f1b1f78293bb00cee$208-212 | Current | Proposal | |-----------|-----------| | {F342758} | {F342760} |4} |