Contributing to Core Tripal

The following guidelines are meant to encourage contribution to Tripal source-code on GitHub by making the process open, transparent and collaborative. If you have any feedback including suggestions for improvement or constructive criticism, please comment on the Github issue. These guidelines apply to everyone contributing to Tripal whether it’s your first time (Welcome!) or project management committee members.

Note

These guidelines are specifically for contributing to Tripal. However, we encourage all Tripal extension modules to consider following these guidelines to foster collaboration among the greater Tripal Community.

Note

Guidelines serve as suggestions ( should ) or requirements (must). When the word “should” is used in the text below, the stated policy is expected but there may be minor exceptions. When the word “must” is used there are no exceptions to the stated policy.

Contents:

• Guidelines for Contribution to Tripal
  • Github Communication Tips
  • Pull Request (PR) Guideline
• Code of Conduct
  • Contributor Covenant Code of Conduct
• Shared Repository Management
  • Branch Naming Conventions
  • Outdated Branches
• Creating a Docker for Testing
  • Testing on the most current development version
  • Testing on an unmerged branch