Guidelines for Work In Progress [WIP] pull requests
juliaelman opened this issue · comments
The guild would like to provide some sort of reference materials or guide for Work In Progress [WIP] pull requests. Here are a few things to help inform what we'd like in the guide:
- What is a Work In Progress [WIP] pull request?
- How do we indicate that something is a WIP?
- Should teammates be reviewing code that is a WIP?
- How do we avoid scope creep on these types of pull requests?
This may belong in the 18F guide instead, but are starting here for now, refs https://handbook.18f.gov/github/#pull-requests
Quote @rogeruiz found:
use the pull request as the master of record for the work related to a feature.
I believe the quote is pulled from Carlos Perez's Pull Request First post.
This is now documented in the CONTRIBUTING.md section.