Fork me on GitHub

@mfikes @alexmiller This appears to be the bot adding the CLA: yes or CLA: no tags.


Yeah, and there are several other bots for GitHub. I haven't been able to find any for JIRA.


From what I can see in the published list of people who have signed a CA, it isn't growing by more than a few per month or so. I wouldn't complain if more if it was automated, but difficult to justify spending a lot of time automating something that isn't taking a lot of time.

Alex Miller (Clojure team)19:09:41

as the one doing the most manual parts of feeding that list, it’s not a big deal

Alex Miller (Clojure team)19:09:50

automating the checking would be useful

Alex Miller (Clojure team)19:09:36

but would also require the feeding to be pretty close to real-time and not involve the manual steps it does now


Yeah, to warrant doing anything it has to be as simple as this website makes it look We've probably spent more time chatting about it than the actual CLA activity going on recently.


I've got some Clojure code that checks whether patches have been signed by someone on a list of submitters or not, but haven't run it much since 2015. It pulls down all patches and among other things, checks whether the author is on a list of submitters that are in a file that I updated manually when I was using it.


I could probably isolate just that part of it and run it weekly while updating the vote counts.


As long as I leave out the older stuff that was checking whether the patches apply cleanly and whether Clojure builds and tests successfully, it would be easy to apply to tickets on CLJ, CLJS, and contrib projects, too, since it would just be checking the author name.


Hah. 🙂 I have a similar project, but it does nothing with respect to CLAs


(Grumble: Most of that stuff is done for you by GitHub and surrounding tooling. Arg.)