Skip to content
This repository has been archived by the owner on May 15, 2020. It is now read-only.

documenting PR approval process defined in #41 #45

Merged
merged 2 commits into from
Mar 5, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,8 @@ improve its performance, do not hesitate to fork and send pull requests.
- Use the same coding style and spacing.
- Open a [pull request][4] that relates to but one subject with a clear
title and description in grammatically correct, complete sentences.
- The pull requests will be merged after a senate majority
of the [Project Leaders][6] approve it. (#41)

#### Modules

Expand All @@ -39,3 +41,4 @@ improve its performance, do not hesitate to fork and send pull requests.
[3]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
[4]: https://help.github.com/articles/using-pull-requests
[5]: http://daringfireball.net/projects/markdown/syntax#img
[6]: https://github.com/zsh-users/prezto/blob/defining-leaders/README.md#project-leaders