Page MenuHomePhabricator

Use callsigns, cards on repository lists
ClosedPublic

Authored by chad on Jan 22 2014, 5:37 AM.
Tags
None
Referenced Files
F14355754: D8036.diff
Thu, Dec 19, 6:18 PM
Unknown Object (File)
Wed, Dec 11, 5:40 PM
Unknown Object (File)
Sat, Dec 7, 6:26 AM
Unknown Object (File)
Thu, Dec 5, 2:50 PM
Unknown Object (File)
Sun, Nov 24, 8:54 PM
Unknown Object (File)
Oct 20 2024, 4:29 AM
Unknown Object (File)
Oct 19 2024, 10:16 AM
Unknown Object (File)
Oct 16 2024, 3:14 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.