github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add workflow diagram to pull request doc

Browse Source
This commit is contained in:
Jeff Lowdermilk 2016-01-15 10:55:24 -08:00
parent 0b04415882
commit c96c04245f
3 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/devel/pr_workflow.dia Normal file
View File

Binary file not shown.

BIN
docs/devel/pr_workflow.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 27 KiB

7
docs/devel/pull-requests.md
View File

@ -34,8 +34,7 @@ Documentation for other releases can be found at
Pull Request Process Pull Request Process
==================== ====================
An overview of how we will manage old or out-of-date pull requests. An overview of how we will manage old or out-of-date pull requests.k
Process Process
------- -------
@ -51,6 +50,10 @@ We want to limit the total number of PRs in flight to:
Life of a Pull Request Life of a Pull Request
---------------------- ----------------------
### Visual overview
![PR workflow](pr_workflow.png)
Unless in the last few weeks of a milestone when we need to reduce churn and stabilize, we aim to be always accepting pull requests. Unless in the last few weeks of a milestone when we need to reduce churn and stabilize, we aim to be always accepting pull requests.
Either the [on call](https://github.com/kubernetes/kubernetes/wiki/Kubernetes-on-call-rotations) manually or the [github "munger"](https://github.com/kubernetes/contrib/tree/master/mungegithub) submit-queue plugin automatically will manage merging PRs. Either the [on call](https://github.com/kubernetes/kubernetes/wiki/Kubernetes-on-call-rotations) manually or the [github "munger"](https://github.com/kubernetes/contrib/tree/master/mungegithub) submit-queue plugin automatically will manage merging PRs.