Goal of this pull request:
to collect comments/ideas/criticism from actual python coders
As I'm not python programmer myself, and not an CI expert either, I hacked this to get away from being stuck at "Build #1" at my project, using Cirrus CI.
Not sure if anything of this is general enough to be pulled into main version, or if I wrote it in a very non-python way, let me know if you have some thoughts about this (but it "WFM" at this moment).
If somebody else want to reuse this kind of hack, keep in mind the revision-counter from git is very flaky value, susceptible to git log history edits, etc.. For me personally this is "good enough", as I don't care too much if I will lose by accident coverage history, but if you need something more solid, it seems to me the least friction path is to just simply add also Travis CI to your project, and use the coveralls native support of it.
Goal of this pull request: to collect comments/ideas/criticism from actual python coders
As I'm not python programmer myself, and not an CI expert either, I hacked this to get away from being stuck at "Build #1" at my project, using Cirrus CI.
Not sure if anything of this is general enough to be pulled into main version, or if I wrote it in a very non-python way, let me know if you have some thoughts about this (but it "WFM" at this moment).
If somebody else want to reuse this kind of hack, keep in mind the revision-counter from git is very flaky value, susceptible to git log history edits, etc.. For me personally this is "good enough", as I don't care too much if I will lose by accident coverage history, but if you need something more solid, it seems to me the least friction path is to just simply add also Travis CI to your project, and use the coveralls native support of it.