-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add citation info to docs and update README badges #236
Conversation
[](https://www.codacy.com/app/nrdg/cloudknot?utm_source=github.com&utm_medium=referral&utm_content=nrdg/cloudknot&utm_campaign=Badge_Coverage) | ||
[] | ||
[](https://www.codacy.com/manual/richford/cloudknot?utm_source=github.com&utm_medium=referral&utm_content=nrdg/cloudknot&utm_campaign=Badge_Grade) | ||
[](https://www.codacy.com/manual/richford/cloudknot?utm_source=github.com&utm_medium=referral&utm_content=nrdg/cloudknot&utm_campaign=Badge_Coverage) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't able to change the coverage badge since codacy believes it hasn't received any coverage info yet. I recommend we open a new issue to fix coverage upload to codacy and don't let it hold up these PRs and the release of v0.4.1.
Question: once we wrap this one up are we ready to make a new release? Or is there any other pending issues that are blocking that? |
This will close one of the remaining issues for v0.4.1. The only other one is to write a publication script for the maintainers and document it in CONTRIBUTING.md. |
Resolves #231