Skip to content

Latest commit

 

History

History
35 lines (20 loc) · 1.6 KB

CONTRIBUTING.md

File metadata and controls

35 lines (20 loc) · 1.6 KB

Contributing

The following is a set of guidelines for contributing to intro-to-data-science.

There are several important ways you can help; here are some examples:

  • Submitting bug reports and feature requests: see Issues.
  • Proposing code or content for bug fixes and new features, then making a pull request.
  • Fixing typos and generally improving the repository.

Code of conduct

We’re fortunate to be part of a large professional community that conducts itself with mutual respect and consideration for others. The Code of Conduct) is part of protecting these features for everyone, everywhere. Please read it.

Commits

We strive to keep a consistent and clean git history and all contributions should adhere to the following:

  1. All tests should pass on all commits
  2. A commit should do one atomic change on the repository
  3. The commit headline should be descriptive and in the imperative

Pull request process

  1. Work on your own fork of the main repo.
  2. Push your commits and make a draft pull request using the pull request template.
  3. When you are happy with your changes, change your pull request to "ready for review", and ask for a code review.
  4. When your code has been approved you should rebase, squash and merge your changes.

License

By making a contribution, you agree that it shall be governed by the terms of the license.