Lines Matching full:requests

10 is accepted into the code base. Changes, in the form of Pull Requests (PR) are
17 Pull requests should be appropriately :ref:`labeled<gh_labels>`,
61 - The project will use the label system to categorize the pull requests.
127 - Pull requests should not be merged without an approval by the assignee.
132 All pull requests need to be reviewed and should not be merged by the author
146 Any change requests (-1) on a pull request have to be justified. A reviewer
156 Pull Requests should have at least 2 approvals before they are merged
165 Reviewers should keep track of pull requests they have provided feedback to
169 the state of the pull request and/or respond to mention requests to see if his
185 Closing Stale Issues and Pull Requests
188 - The Pull requests and issues sections on Github are NOT discussion forums.
191 - In case of both issues and pull-requests the original poster needs to respond
195   response the item may be closed (draft and DNM tagged pull requests are
247 Labeling issues and pull requests in GitHub
250 The project uses GitHub issues and pull requests (PRs) to track and manage
255 All GitHub issues or pull requests must be appropriately labeled.
309 feature requests are handled and become features can be found in :ref:`Feature
312 Labels applicable to pull requests only
355 Labels applicable to both pull requests and issues