mirrors/PowerShell
0
0
Fork 0
mirror of https://github.com/PowerShell/PowerShell.git synced 2024-11-23 17:53:58 +08:00
Code Issues Packages Projects Releases Wiki Activity
7762d7bf49
PowerShell/docs/maintainers/pull-request-process.md
Zachary Alexander 7d5367a9f7 Small grammar change to pull requests guide (#4322) 
him -> them, which is consistent with usage above.
2017-08-04 14:59:16 -07:00

2.3 KiB
Raw Blame History

Pull Request Process

Requirements for a pull request to be accepted into PowerShell

  • Writing tests
  • Writing documentation

Pull Request Workflow

  1. A contributor opens a pull request.
  2. The contributor ensures that their pull request passes the [CI system][ci-system] build.
  • If the build fails, a Repository Maintainer adds the Review - waiting on author label to the pull request. The contributor can then continue to update the pull request until the build passes.
  1. Once the build passes, the maintainer either reviews the pull request immediately or adds the Review - needed label.
  2. An Area Expert reviews the pull request code.
  • If the contributor does not meet the reviewer's standards, the reviewer makes comments. A maintainer then removes the Review - needed label and adds the Review - waiting on author label. The contributor must address the comments and repeat from step 2.
  • If the contributor meets the reviewer's standards, the reviewer comments that they are satisfied. A maintainer then removes the need review label.
  1. Once the code review is completed, a maintainer merges the pull request.

Abandoned Pull Requests

A pull request with the label Review - waiting on author for more than two weeks without a word from the author is considered abandoned.

In these cases:

  1. Ping the author of PR to remind them of pending changes.
  • If the contributor responds, it's no longer an abandoned pull request, proceed as normal.
  1. If the contributor does not respond within a week:
  • If the reviewer's comments are very minor, merge the change, fix the code immediately, and create a new PR with the fixes addressing the minor comments.
  • If the changes required to merge the pull request are significant but needed, create a new branch with the changes and open an issue to merge the code into the dev branch. Mention the original pull request ID in the description of the new issue and close the abandoned pull request.
  • If the changes in an abandoned pull request are no longer needed (e.g. due to refactoring of the code base or a design change), simply close the pull request.