Pull Request Guide

• Fork from microsoft/maro, send a pull request back.

  • Avoid huge pull requests.

• Branch Naming Code:

  • master, it hosts the latest, stable features.
  • vx.y, it is a stable branch for version control, which will freeze the feature list after a new version born.
  • vx.y_investigation_zzz, it is an investigation branch for version branch vx.y.
  • vx.y_experiment_zzz, it is an experiment branch for version branch vx.y.
  • vx.y_bug_zzz, it is a bug fixing branch for version branch vx.y.
  • vx.y_issues_zzz, it is an issue resolving branch for version branch vx.y.
  • vx.y_feature_zzz, it is a feature branch for version branch vx.y.
    • vx.y_feature_zzz.task_uuu, it is a task branch for feature branch vx.y_feature_zzz.
    • vx.y_feature_zzz.bug_uuu, it is a bug branch for feature branch vx.y_feature_zzz.

• Git branch management

  • When requesting a PR, if possible, use rebase rather than merge. Rebase is the better choice in most cases.
  • Make sure the PR's size (number of changed files) is moderate. If the PR is too large, split it into multiple ones.