Add https://lgtm.co about postcss.org HOT 15 CLOSED

Nope :). But I anyway will be around :).

from postcss.org.

@mxstbr You can customize pattern and accept :+1: or anything ;)

from postcss.org.

Sure, I think @MoOx could be a good asset too if he has time for it.

Isn't it good enough if one of the members accepts it, why all? It seems like a lot of work and waiting...

from postcss.org.

Mainly so my mistakes don't slip through cracks, but if I'm the only one in the file it doesn't really make sense to have it. :)

from postcss.org.

You can configure who many I think.

from postcss.org.

That's true, maybe we can add some more "validators" that has enough experience to approve code.

@jonathantneal , @stephenway ?

from postcss.org.

I think it's enough if two people in the MAINTAINERS file approves the PR before merge for starters.

from postcss.org.

I like that!

from postcss.org.

Sounds great, count me in for that.

from postcss.org.

I can help if we can define me as "optional" (I mean not required all the time)

from postcss.org.

@ai can you either add me to the postcss team or enable LGTM for this repo on https://lgtm.co?

from postcss.org.

I am in the city. Can I add it today evening, when I will be near my laptop?

from postcss.org.

Yeah definitely, don't worry about it!

2016-01-08 16:52 GMT+01:00 Andrey Sitnik [email protected]:

I am in the city. Can I add it today evening, when I will be near my
laptop?

—
Reply to this email directly or view it on GitHub
#34 (comment).

from postcss.org.

@ai I just took the liberty to handle this. @mxstbr have been invited.
Btw, github ask to migrate the org to new roles and shit, so I did that. Note that for now (as it was before) everybody is an owner. Trust is key imo :)

from postcss.org.

@MoOx thanks, LGTM.co is now enabled for this repo!

from postcss.org.