rfc:github-pr
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| rfc:github-pr [2014/10/30 21:48] – created jbafford | rfc:github-pr [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== PHP RFC: GitHub Pull Requests Triage Team ====== | ||
| * Version: 1.0 | * Version: 1.0 | ||
| * Date: 2014-10-30 | * Date: 2014-10-30 | ||
| * Author: John Bafford, john@bafford.com | * Author: John Bafford, john@bafford.com | ||
| - | * Status: | + | * Status: |
| * First Published at: http:// | * First Published at: http:// | ||
| Line 15: | Line 16: | ||
| Each PR may have one or more labels, as relevant: | Each PR may have one or more labels, as relevant: | ||
| - | rfc | + | * rfc |
| - | bug (fixes a bug; preferably with a pointer to the relevant bugs.php.net entry) | + | |
| - | feature-request (a feature request that does not have an RFC) | + | |
| - | tests | + | |
| - | docs (documentation) | + | |
| - | trivial (typo fixes, whitespace fixes, etc) | + | |
| - | misc (stuff that has been triaged, but does not clearly fall into any category) | + | |
| Applying labels will require write access to the GitHub repository. (This implies that whomever has access to do this will have to be trusted to not change the GitHub repository, so as not to break the mirroring tools, or introduce changes to the GitHub repository other people might clone and use.) | Applying labels will require write access to the GitHub repository. (This implies that whomever has access to do this will have to be trusted to not change the GitHub repository, so as not to break the mirroring tools, or introduce changes to the GitHub repository other people might clone and use.) | ||
| Line 45: | Line 46: | ||
| ===== Future Scope ===== | ===== Future Scope ===== | ||
| There are a number of automated processes the PR triage team could use which may help, such as (but not necessarily limited to): | There are a number of automated processes the PR triage team could use which may help, such as (but not necessarily limited to): | ||
| - | * automatically closing idle PRs | + | |
| - | * noting when a travis test is failing and alerting the submitter to take corrective action | + | * noting when a travis test is failing and alerting the submitter to take corrective action |
| Line 63: | Line 64: | ||
| ===== Rejected Features ===== | ===== Rejected Features ===== | ||
| (No rejected features at this time.) | (No rejected features at this time.) | ||
| - | |||
rfc/github-pr.1414705716.txt.gz · Last modified: 2017/09/22 13:28 (external edit)