devth/yetibot

View on GitHub
CONTRIBUTING.md

Summary

Maintainability
Test Coverage
# Yetibot :heart: PRs

Before adding to Yetibot you might want to check with the author first to see
if:

1. the feature makes sense for Yetibot
1. whether it should be in `yetibot` or `yetibot.core`
1. no one is [working on it already](https://github.com/yetibot/yetibot/labels/in%20progress)

When ready to contribute:

1. Fork the repo
1. Add your contributions on the `master` branch of your fork as logically
   grouped commits with [well-formed commit
   messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
1. Rebase on upstream master if it changed
1. Open a PR

## Tests

Tests are appreciated, especially when there's logic beyond a simple API call.

## Style

Please adhere to yetibot's existing conventions:

- 2 spaces
- no lines beyond 80 characters wide
- no trailing whitespace

![thanks](doc/thanks.jpg)

## Merging PRs

- If an outside contributor submits a PR, it is up to a core team member to
  review and merge the PR
- When a [core team member](https://github.com/orgs/yetibot/people) submits a
  PR, the author should merge their own PR after it is reviewed and tests pass