Open Bug 1472215 Opened 7 years ago Updated 6 years ago

Add link from diffusion to the commit in the observed repository

Categories

(Conduit :: Phabricator, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: tjr, Unassigned)

Details

(Keywords: conduit-triaged)

I got a herald email for this commit: https://phabricator.services.mozilla.com/rMOZILLACENTRALf6f4a6276102 There is no way to follow to the hg.mozilla.org repo (https://hg.mozilla.org/mozilla-central/rev/f6f4a6276102) nor is there any way to actually search the commitdiff for what my Herald is about.
It would be nice if the at least the page linked to had a link to the upstream repository (and/or searchfox, if appropriate), even if the email doesn't have a link.
Our Bugzilla + Phabricator setup is pretty non-standard, so we'd need to be maintaining email modifications to link to bugzilla ourselves. The maintenance burden here probably outweighs the use, so I'm considering that a WONTFIX. Adding a bugzilla link to the diffusion page (the repository browser on Phabricator) is probably much more doable, so morphing to that.
No longer blocks: 1472210
Keywords: conduit-triaged
Summary: Herald emails do not link to the commit in the remote repository → Add link from diffusion to the commit in the observed repository
Whiteboard: [phabricator-backlog]
This isn't about linking to bugzilla, but to hg.mozilla.org, though. I assume that phabricator knows about that, because it either polls it, or receives pulse messages from it.
(In reply to Tom Prince [:tomprince] (limited availability Jul 16-29) from comment #3) > This isn't about linking to bugzilla, but to hg.mozilla.org, though. I > assume that phabricator knows about that, because it either polls it, or > receives pulse messages from it. Right, totally mistyped the "adding a bugzilla link"... should be "adding an hg.mozilla.org link" (consistent with the new summary).
Keywords: conduit-backlog
Whiteboard: [phabricator-backlog]
Keywords: conduit-backlog
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.