E. Dunham
E. Dunham
@str4d please make sure the refactor passes flake8 -- https://travis-ci.org/servo/homu/jobs/230962270
Heard back from github support: > To answer your question, you must have at least Read permission on a repository to be assigned an issue so the teams implementation could...
Today I learned about https://github.com/eeyorebot/eeyore, which might have the features to address this issue.
Should this be a specific new label, like merge-on-success, or any label?
Build status seems to be available in the API result as "state":"failure", see https://github.com/servo/highfive/issues/16 for a couple examples
@Mylainos Welcome! I believe it should be in `status_updates/__init.py__`, but let's confirm with @jdm since he architected the change to event handlers.
In Servo, this could be a link to http://servo.github.io/servo-starters/ . In other repos, this could be - any open, easy-tagged issue without an "assigned" label if the repo has an...
Windows: An appveyor.yml was added but Appveyor wasn't switched on. I've added the project to Appveyor and builds should be visible at https://ci.appveyor.com/project/servo/ipc-channel.
I don't actually see a comment saying that anyone flipped the switch on the Appveyor side after landing the appveyor.yml. @larsbergstrom, is Appveyor enabled through your account for this repo?...
@larsbergstrom Thanks for clarifying! My bad on creating it under the free account; I incorrectly remembered Servo as being the centralized account for stuff.