Skip to content
Robert Widmann edited this page Sep 13, 2013 · 4 revisions

Overview

The MailCore team gladly welcomes any pull requests that meet any of the following criteria:

  • Bug Fixes / Patches
  • Critical Features
  • Documentation

Pull Requests

Pull Requests are much preferred over issues if you know how to fix a bug or implement a feature. Pull Requests should try to address one issue at a time, and/or limit the scope of any changes (you can always divide one large pull request over many smaller ones). Pull Requests go through a short Code Review, and may be closed due to inactivity.

Staying Up-To-Date

All pull requests should be implemented on a branch of a fork of MailCore2 that is as up to date as possible. To make it easy to stay up to date, it is recommended that you run the following command immediately after cloning MailCore2:

git remote add upstream https://github.com/MailCore/mailcore2.git

After that, it is recommended that you run the following commands every so often to guarantee that you have the latest version (Hub aliases these commands to git pu):

git fetch origin -v
git fetch upstream -v
git merge upstream/master