On May 18, 2013, at 16:36, Dan Burkert wrote: > Attached are two patches for codeq. The first adds support > for importing repositories into codeq directly from github > through the github API, as well an improved CLI for codeq > (necessary for specifying a github import). The second > patch builds on the first and adds the ability to import git > ref types (tags and branches) into codeq.
Very cool! These look like very useful extensions. I've been speculating about the possibility of using Storm to run a production Codeq installation. Basically, it would be called into action whenever a monitored event (eg, git commit or push, test run, Clojars update) occurred. I have a few specific questions, but more generally, I'd like to know what you've found out in extending and using Codeq: What mechanisms are you using to manage and run Codeq? What support would you want in a production release? What other import facilities would you like to have? Like that... -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume r...@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Software system design, development, and documentation -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
