-
Add code coverage tools badge
-
This issue tracks the implementation of the [Jazzband guidelines](https://jazzband.co/about/guidelines) for the project [django-superform](https://github.com/jazzband/django-superform)
It was initi…
-
Running tasks in our Github CI locally is a bit complex now. By moving some parts of it to `cargo xtask` can both simplify the CI and allow to run CI tasks on a local machine. Adding reporting a code …
i386x updated
8 months ago
-
I am not sure what's your stance on code coverage (imho a useful metric to orientate ourselves and prevent regressions, but something not to be abused in trying to hit 100% coverage by creating meanin…
-
This issue tracks the implementation of the [Jazzband guidelines](https://jazzband.co/about/guidelines) for the project [Watson](https://github.com/jazzband/Watson)
It was initiated by @jmaupetit who…
-
https://shields.io/badges/ で作れるやつを参考にする
https://github.com/ndxbn/bun に適用する
- [x] [Codacy](https://www.codacy.com/)
- [x] [Code Climate](https://codeclimate.com/)
- [x] [Codecov](https://about.codeco…
-
## Problem to solve
There is expressed confusion about the differentiation in team vs pro plan selection. Example from customer here: https://sentry.zendesk.com/agent/tickets/116691 and [here](https…
-
Coming from https://github.com/w3c/wot-testing/issues/189
Once a Thing is tested via its TD where multiple requests are sent to the Thing, it would be nice to incorporate this information to TD, si…
-
Just starting a discussion about what preferences we would have regarding the publication workflow.
## CI/CD
I'm assuming we would want some form of CI/CD setup, in the past @andylaw used Travis C…
-
Following up on #37, a few minor details were left unfinished:
- [ ] Set up a pre commit config to run tests/linting locally
- [ ] Define any linting parameters
- [ ] Setup code coverage to track…