- User Since
- May 28 2013, 8:40 PM (247 w, 3 d)
Aug 31 2017
@epriestley was just curious if any of the "Real Working Examples" could be brought into the resource folder in phabricator, this information is super useful and helps complete the product.
Jun 7 2017
Have a most recently accessed repo list in there somewhere. Right now the order is always listed by most recently updated repo shows at the top. Maybe a additional column in there that shows most frequented repos? or maybe a "favorites" list for repos. A user can have access to many repos but not use them frequently, so pushing them towards the bottom.
Feb 1 2017
Oct 13 2016
I'm so excited about this ticket :)
Aug 16 2016
I'm super excited about this feature.
Aug 8 2016
Jun 28 2016
Please add the triple dash to the documentation page, I couldn't find it clicking on the main life-saver icon link.
Apr 26 2016
@epriestley I updated the description in this ticket.
Mar 10 2016
nothing added to commit but untracked files present (use "git add" to track)
root@phabricator:/home/phabricator/phabricator# git log -1
Author: Chad Little <email@example.com>
Date: Fri Feb 19 14:45:05 2016 -0800
Feb 12 2016
I had to rename all those junk records just so I could hide them after the fact.
Wow. This is awesome. I'm glad you were able to find and trace down this issue with what minimal info I could provide. I'll try to give better descriptions in the future. It would also be nice to remove columns that have no tickets associated with them.
These are sub projects imported from another project. But they never existed before when I originally imported their workboards. So I was as confused as you to how they suddenly started showing up.
I just updated code early in the day, like 2am.
Aug 19 2015
I think it would be useful if there is not a "login as" to atleast test objects based on specific usernames.
Nov 22 2014
I second this. At my company we are running into lots of dups. We used to use trac, and our CEO uses crap like this to tell us that phab is not as good as trac. I don't like having to argue this point. I think having a auto-complete would be a great thing to have. but instead of below like a search engine, show like a container below search which has a list similar to the one that popups like the "Edit Blocking Tasks" modal. This would probably add additional performance requirements on the server. But make it optional, and tell the administrator that they should consider setting up an elasticsearch server on the machine to use this feature.