-
This issue tracks the implementation of the [Jazzband guidelines](https://jazzband.co/about/guidelines) for the project [django-invitations](https://github.com/jazzband/django-invitations)
It was ini…
-
## Steps to reproduce the problem
I've reproduced this with the [Resolwe](http://resolwe.readthedocs.io) project:
```
git clone https://github.com/genialis/resolwe.git
cd resolwe
mkvirtualenv res…
-
For example [Pydjantic](https://github.com/ErhoSen/pydjantic) :)
-
## Description
I’d like to have a test coverage badge in the readme to give package users a sense of the state this project is in. Users should be able to see the percentage of code that is covered…
-
I added this to check test coverage. I would recommend adding this since it will be useful as package gets more users, contributors.
https://github.com/openjournals/joss-reviews/issues/4588
-
![image](https://user-images.githubusercontent.com/7644758/82023424-8c349480-968e-11ea-99fe-0ed193f9a9a4.png)
-
**Date accepted:** 2023-03-30
Submitting Author Name: Rex Parsons
Submitting Author Github Handle: @RWParsons
Other Package Authors Github handles: @robinblythe, @agbarnett
Repository: https:/…
-
The automated test suite should be run in a Github pipeline /action. I'm not sure this is a requirement of JOSS, but systematically running the test suite at each commit helps catching bugs early. The…
-
Created on behalf of @pgiffuni
It would be really nice to get the Coverity automation working on github. Just to give ourselves something else to co ;).
-
Let's add coverage reporting, as it's done for example in `eo-files` repo. Check the `codecov.yml` file they have in GitHub Actions. Also, don't forget to add the badge to README.