👍🎉 Thank you taking the time to contribute! 🎉👍
The following is a set of guidelines for contributing to blockfrost-dotnet
and its packages.
These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
This project and everyone participating in it is governed by the blockfrost Code of Conduct. By participating, you are expected to uphold this code.
- Blockfrost.Api
- Blockfrost.Cli
Check if the issue is already tracked.
If not, open a Bug report
Check if the enhancement is already tracked.
If not, open a Feature request
Unsure where to begin contributing to Atom? You can start by looking through these beginner
and help-wanted
issues:
- Beginner issues - issues which should only require a few lines of code, and a test or two.
- Help wanted issues - issues which should be a bit more involved than
beginner
issues.
Please follow these steps to have your contribution considered by the maintainers:
- Follow all instructions in the template
- Follow the styleguides
- After you submit your pull request, verify that all status checks are passing
What if the status checks are failing?
If a status check is failing, and you believe that the failure is unrelated to your change, please leave a comment on the pull request explaining why you believe the failure is unrelated. A maintainer will re-run the status check for you. If we conclude that the failure was a false positive, then we will open an issue to track that problem with our status check suite.
While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional design work, tests, or other changes before your pull request can be ultimately accepted.
- Use Markdown.