When contributing to this repository, please first discuss the changes you wish to make via an issue, email, or any other method, with the owners of this repository before issuing a pull request.
To report a bug or suggest a new feature, please go to the monarch-initiative/monarch-phenotype-profile-ingest issue tracker, as we consolidate issues there.
Please supply enough details to the developers to enable them to verify and troubleshoot your issue:
- Provide a clear and descriptive title as well as a concise summary of the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
- Provide screenshots of the expected or actual behaviour where applicable.
- Create a bug fix or feature development branch, based off the
mainbranch of the upstream repo, and not your fork. Name the branch appropriately, briefly summarizing the bug fix or feature request. If none come to mind, you can include the issue number in the branch name. Some examples of branch names are,bugfix/breaking-pipfile-errororfeature/add-click-cli-layer, orbugfix/issue-414 - Make sure your development branch has all the latest commits from the
mainbranch. - After completing work and testing locally, push the code to the appropriate branch on your fork or origin repository.
- Create a pull request from the bug/feature branch of your fork to the
mainbranch of the upstream repository.
NOTE: All the development must be done on a separate branch, either in your fork or in the origin repository. The main branch of the upstream repository should never be used for development.
ALSO NOTE: github.com lets you create a pull request from the main branch, automating the steps above.
A code review (which happens with both the contributor and the reviewer present) is required for contributing.