Skip to content

Latest commit

 

History

History
35 lines (18 loc) · 1.82 KB

CONTRIBUTING.md

File metadata and controls

35 lines (18 loc) · 1.82 KB
Raw

How to contribute to iReceptor

Did you find a bug?

  • Ensure the bug was not already reported by searching on GitHub under Issues.

  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.

  • The iReceptor team uses Jira to manage the coordination of internal development. Once your issue is being addressed by the team, it will be assigned a Jira issue ID of the form IR-NNNN and patches and discussion will use that ID.

Did you write a patch that fixes a bug?

  • Open a new GitHub pull request with the patch.

  • Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

Did you fix whitespace, format code, or make a purely cosmetic patch?

Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the iReceptor platform will generally not be accepted.

Do you have questions about the source code?

Please join us!

The iReceptor project is only as strong as the community around it, and we rely on our colleagues in the AIRR Community and beyond to contribute. We encourage you to pitch in and add your suggestions.

Thanks!

The iReceptor Team

Attribution

These contribution guidelines are based on the excellent Ruby on Rails contribution guidelines