One more thing before I go to bed -- today I made a fix for what I would consider to be a bug in codeq importing. In the case where you are importing a fork of a project that you have already imported, the forked project is not associated with the commits already in the parent repo. In the attached diagram this corresponds to the purple area. A more specific example: I import Datomic/codeq into my codeq db, which results in ~50 imported commits. I then import my fork, danburkert/codeq, which results in ~30 new commits. The original 50 commits are not associated with my fork, so they will not appear in a query asking for all the commits of danburkert/codeq. This commit<https://github.com/danburkert/codeq/commit/910e5e1f8c69c43653a0a922d57b4c9a7e62655d> fixes the issue, I can make a patch if there is interest.
-- Dan -- -- 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.
<<attachment: codeq-import.svg>>
