Page MenuHomePhabricator

Use callsigns, cards on repository lists
ClosedPublic

Authored by chad on Jan 22 2014, 5:37 AM.
Tags
None
Referenced Files
F19073465: D8036.id.diff
Mon, Dec 1, 2:06 AM
F19070282: D8036.diff
Sun, Nov 30, 3:54 PM
F18943725: D8036.diff
Nov 11 2025, 2:33 PM
F18843930: D8036.id.diff
Oct 29 2025, 2:01 AM
F18842255: D8036.diff
Oct 28 2025, 2:28 PM
F18818930: D8036.id18180.diff
Oct 22 2025, 3:17 AM
F18804305: D8036.diff
Oct 18 2025, 7:17 AM
F18220058: D8036.id18184.diff
Aug 19 2025, 1:42 PM

Details

Summary

Minor, adds the Callsign and changes to cards view when listing repositories.

Test Plan

Reload sandbox list of repositories, see new items.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

This should be rXYZ instead of XYZ, similar to how we list T123 instead of just 123.

(If you really want, you could define getMonogram() and use it here.)

So anytime we display a repository callsign to the user, we want it as

rCALLSIGN

?

Its slightly inconsistent right now so I just wanted to make sure I understood the direction.

I can see it being slightly confusing, for example, my git folder has PCORP, not rPCORP in it.

Anywhere where you'd use T123 if it was a task, use rABC.

Anywhere you'd use 123 if it was a task, use ABC.

Basically, callsigns are just like more-memorable IDs.

I think we're mostly consistent about this -- what are the exceptions you're aware of?

Only saw one spot so far. For example, https://secure.phabricator.com/diffusion/P/ - in the object detail pain, the "Callsign: P" part should be "Callsign: rP" maybe? Although in the "what would you do if this were a task?" mindset, I'd just remove that field altogether.