Skip to content

Instantly share code, notes, and snippets.

@SZanlongo
Last active June 5, 2019 14:50
Show Gist options
  • Save SZanlongo/72fa8e8659b35ce1c5cc53d65eae8713 to your computer and use it in GitHub Desktop.
Save SZanlongo/72fa8e8659b35ce1c5cc53d65eae8713 to your computer and use it in GitHub Desktop.
Contributing to Project Template

From Pi-hole project: https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md

Contributors Guide

Please read and understand the contribution guide before creating an issue or pull request.

Etiquette

  • Our goal for $project$ is stability before features. This means we focus on squashing critical bugs before adding new features. Often, we can do both in tandem, but bugs will take priority over a new feature.
  • Please be considerate towards the developers and other users when raising issues or presenting pull requests.
  • Respect our decision(s), and do not be upset or abusive if your submission is not used.

Viability

When requesting or submitting new features, first consider whether it might be useful to others. Projects are used by many people, who may have entirely different needs to your own. Think about whether or not your feature is likely to be used by other users of the project.

Procedure

Before filing an issue:

  • Attempt to replicate and document the problem, to ensure that it wasn't a coincidental incident.
  • Check to make sure your feature suggestion isn't already present within the project.
  • Check the pull requests tab to ensure that the bug doesn't have a fix in progress.
  • Check the pull requests tab to ensure that the feature isn't already in progress.

Before submitting a pull request:

  • Check the codebase to ensure that your feature doesn't already exist.
  • Check the pull requests to ensure that another person hasn't already submitted the feature or fix.

Technical Requirements

  • Submit Pull Requests to the development branch only.
  • Before Submitting your Pull Request, merge development with your new branch and fix any conflicts. (Make sure you don't break anything in development!)
  • Please use the Google Style Guide for your code submission styles.
  • Commit Unix line endings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment