I doint know if we can make it an array.

@20after4 and @epriestley may we can do

My workflow is find the parent task, click merge in, then select all open tasks and 9/10 times it's in the pane, select and go. I generally don't copy and paste the task ID. I don't always know if I'll find a duplicate, so I don't always copy the task ID before searching around.

One thing you could try is launching a test instance on Phacility and see if you have any issues with your Repository there. That would determine if its an issue in Phabricator or with your local configuration.

I have a warning for old database version

Other than this i have tried importing from a different svn server but no luck so far.

The Fedora QA phabricator instance uses persona and has been using it since December 2014.

Too many deck slots, product literally unplayable.

Wait are they not Blizzard colors any more? My team can't handle using different colors from WoW and Diablo III and will find this feature too confusing if they have to learn about ponies too. Phabricator is ruined forever.

FUN POLICE HERE

This is fairly messy and probably not worth fixing until the surrounding code is more modernized.

T7805 was the "use applicationsearch in the dialog" task.

I think this default ("all my open stuff") is probably the right one for "Edit Dependencies" and "Edit Maniphest Tasks" from Differential, and for "Edit Blocking Tasks", "Edit Pholio Mocks" and "Edit Differential Revisions" in Maniphest, although the argument for some of those is a little weaker.

In my flow I essentially only ever merge by copying the task ID, so the filter doesn't matter at all. Do you tend to search for the task by name?

Ah, interesting. I wasn't aware it was gone in PHP7. Given that, I agree that this probably isn't worth supporting (I've never seen this syntax in the wild myself).

P.S. It's not an April Fool's joke....

I guess you can tell from the history that I put together a patch to fix this and submitted it as a differential revision. I hope it may be considered appropriate for inclusion (and am wiling to do further work on it to bring it up to standard if necessary). Thanks for a great product!

@epriestley I can add <script language="PHP">... support to XHPAST if you'd like, but since it's removed from PHP7 and never was really mainstream I don't believe it's worth the effort.

Doesn't seem specific to php.

Ouch. Burned.

Haha. Yes, well, you claim in another file that it was WoW colors. Get your story straight, @chad !

I guess I am the only one with elite Pony knowledge here.

It was mostly a comment that the title of this task was "Allow Badges to be ordered by Rarity" as in Rarity from My Little Pony and not just rarity.

Did I get the colors wrong? I thought I copied them as they were...

In this specific case (staging same as origin) we could just not push the base tag (it has no value in this case). We can probably even figure that out automatically without needing configuration. That would be a cleaner fix, I think?

http://mlp.wikia.com/wiki/Rarity

yoink

Thanks!

I'll definitely use my powers for evil. Thanks :)

Sounds good. I added you to Community so you should have sweeping administrative powers now.

I ended up creating a custom extension.

The more modern, slightly more concise process is:

One additional usecase for subprojects: it would be very nice to be able to move subprojects between different parents. In particular lets say we have
team1 > productA
team1> productB
team2> productC
and as a result of a re-org or some other influence productA moved to team2. To do the move now we'd have to create a new project, reconfigure it (cloning the workboard), and mass change the labels (remembering where in the workboard every task is).

We are planing to use subprojects in two variants:

When using a repo as its own staging, I kinda hoped that we won't be using refs/tags/ but refs/phabricator/ or something, so when cloning, the default would be "do not clone all staging things".

I'm thinking for my case, there's not really a lot of value in keeping the tags around after the diff has been closed. Maybe that's something to consider?

I probably wouldn't show them in the UI for now, although I don't think adding an "Other Refs" table underneath tags/branches on the main screen with, say, 5 entries and a "See All" button would necessarily be terrible if anyone can come up with a reason that users might ever care about it.

When I said "user images" above, I meant to say "user uploaded images" like what you drag & drop in Pholio, Phriction, Maniphest, etc... i.e. explicitly not Phab built-in images which are indeed cached. Sorry if that was confused with "user profile images". There are no performance problems here. In general I have observed no performance issues with Phacility outside of the matter tracked by this very task.

User profile images should be getting cached. For example, your profile image here:

I've really never experienced any poor performance when using phabricator. It's not blazing fast but that is mostly due to the complexity of the server side php bits. I have literally never seen slowness in loading static resources.

I've been using this functionality for some days to use the CircleCI integration. Mostly the user experience is fine. It's mostly possible to configure git log to ignore these tags, like:

i just tried diffrent protocol. HTTPS vs HTTP.

Here's another big problem (IMHO) I just realized: using Phab on mobile or through tethering on your laptop is terrible: the fact user images don't get cached, kills usability: it takes forever to load / reload anything with user images.

Wikimedia is definitely interested in this one.

@csteipp was one of the people who originally advocated for such strict file visibility enforcement. He would be the best one to respond with justification for wanting the feature in the first place.

In T10429#167793, @chad wrote:

Personally I would probably want a means of filtering out inferred memberships, but maybe it sounds like you're OK with them, and just want inferred projects labeled as such?

yes. used that document for troubleshooting purpose.

Personally I would probably want a means of filtering out inferred memberships, but maybe it sounds like you're OK with them, and just want inferred projects labeled as such?

Root problem (a) is that the query lists sub-projects which I am a member of, and additionally it lists the parent project, which I am not directly a member of, but only through the sub-project. This is confusing, because I am listed as "joined" to project which I never really joined.

Root problem (a) is that the query lists sub-projects which I am a member of, and additionally it lists the parent project, which I am not directly a member of, but only through the sub-project. This is confusing, because I am listed as "joined" to project which I never really joined.
Root problem (b) is that several projects in the list might logically belong to a parent project, but are not shown in this way. This is confusing in general, because (1) a project's sub-projects are scattered all over the list, making it difficult to grasp as a whole, and (2) the correct interpretation of a project's name might depend on its parent project.

We run basically all our company todos in Phabricator. Example user scenarios that I'd like to see covered with this feature:

There is no direct path that will work for all installs and not be likely janky UI-wise. For example you might be a member of a project 4 levels down, what are you expecting to see? The best I can come up with is a "only parents" checkbox on the search query, which would return only projects that are parents, and then group their direct children.

This request has the same design issues that showing all levels on a project's tag. Given both the number of levels (16) and the number of direct children (99+).

Sounds good. Let us know if you run into anything else.

Thanks @epriestley, it makes sense what you say.

You can register an event listener for the TYPE_AUTH_WILLREGISTERUSER event. We are generally moving away from this system, but it works today and I don't have any near-term plans to replace it in this case. This is the documentation:

Another possible solution would be a query option for projects this you can control if you all projects (including subprojects) or just top level projects.

I haven't been successful locally in getting a GC'd node to reach an appreciable level of memory consumption, and the production servers are currently at ~1.5GB.

I think the ~1.5GB node instance size is also expected.

In T10350#167753, @rbalik wrote:

This is useful, but are there any plans to add this functionality to the GUI? Would be nice to have for when we're doing some housekeeping

This is useful, but are there any plans to add this functionality to the GUI? Would be nice to have for when we're doing some housekeeping

D14879 made hovercards smart about these sort of things (But hovercard don't have a little arrow thingy).

See T10350.

Is there any way to take an existing project and make it into a subproject? I don't see any discussion of that in here

Sorry, Vehicle VIN Identification Numbers.

(It mostly has reference stuff like our vehicle VIN numbers, our PG&E account number and credentials, etc. If you hack it, you can pay our electric bill!)

There is, but we don't use it very much.

Is there an internal Phabricator for the Priestley household where you assign him stuff as well?