This is getting so cloooose. Can't wait to get coverage working and finally move my last repository for GitHub
I just need to figure out how to persist the metadata so I can link to the trunk branch's badge. Everything else is not nearly as important for now
I'll probably just use MariaDB since I'm already using that for Gitea. That will require a whole database interaction and bleh
Anyways I tagged 0.1.0, maybe I can get back to this in another week - I have a lot at work to deal with.
Also, I just remembered that I will have to deal with integrating a new CI at the same time, since Travis evidently doesn't support any other platforms than GH.
Drone CI looks pretty nice.
Mini roadmap for ao-coverage Show more
0.2.0: metadata (branch commit links mainly)0.3.0: bash script to help CI integrate seamlessly0.4.0: Dockerfile + integrations0.5.0->1.0.0: more metadata if need be
0.2.0 down, just have the bash script and Dockerfile to do as well as ironing out issues and writing tests to get some good coverage (heh). I think I could do it all for 0.3.0
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!