👍 worked fine for me, thank you!

No, that was some stray debugging code. I updated the script.

Ah cool, I think that'll work, noticing this:

UPDATE `phabricator_maniphest`.`maniphest_task` SET points = 2 WHERE id = 4130;
UPDATE `phabricator_maniphest`.`maniphest_task` SET points = 2 WHERE id = 4129;
HAS POINTSHAS POINTSUPDATE `phabricator_maniphest`.`maniphest_task` SET points = 0 WHERE id = 4201;
HAS POINTSHAS POINTSHAS POINTSHAS POINTS

You may be able to just comment out that check, but I'm not sure how the extension stores its data. You'd have to check with the authors to be sure.

We're using the wikimedia sprint extension, which adds a isdc:sprint:storypoints field - upon running ./copy_points.php --field isdc:sprint:storypoints, we get

[2016-02-16 18:46:22] EXCEPTION: (PhutilArgumentUsageException) Field "isdc:sprint:storypoints" is not an "int" field, and can not be migrated. at [<phabricator>/copy_points.php:62]
arcanist(head=master, ref.master=fcc11b3a2781), phabricator(head=master, ref.master=608fcdd9dd70, custom=2), phutil(head=master, ref.master=f43291e99d36), sprint(head=master, ref.master=802afc636035)

Thanks!

Yeah -- you're actually going to extend HeraldField. A good place to start might be DiffusionPreCommitRefPusherProjectsHeraldField. Basically:

Ok, thank you for your answer.
One last thing, is it possible to implement custom conditions as it is for custom actions? I haven't read about this anywhere.

got it. thanks

If you want to block a push when a user has too many open reviews, you need to write a new condition, not a new action. Your rule will look like this:

Sorry for that, I added it at the beginning. We'd like to try to make people do their code reviews more often, and not let them pile up while writing some new features.

This is a feature, not a bug.

Please describe the root problem when requesting a feature. See Contributing Feature Requests. If you aren't sure what we mean, see Describing Root Problems for some more details.

okay - I'll just fix this

I can't reproduce this. Here's what I did:

I think this should be fixed in HEAD, let me know if I missed anything. Thanks for the report (and the patches; I did approximately the same thing in D15282).

We have this config (which I think setup issues recommend) but that should be the only difference between this and other installs, I think:

ok so that was the exact phrase that when searched didn't show up, it works fine here

Unless, perhaps, "long" was really quite long indeed.

Notes on setting up Vagrant with libvirt support

No luck on that one either. :)

Hmmm... pneumonoultramicroscopicsilicovolcanoconiosissupercalifragilisticexpialidocious

I added you to Community.

I think we were using strings that were too long when checking this out on our production install.

I can't close this task to spite myself.

Can't reproduce:

untalcumish

New watch stuff should be live now.

Also probably related to T8831.

I didn't immediately even know I was on a Milestone. I should probably put more thought into the tag UI.

Yeah, that's buggy. I think I that only got partially implemented. My plan is:

Should I be able to watch a Milestone? https://secure.phabricator.com/project/profile/1418/ clicking "Watch Project" just reloads the page with no changes.