Lines Matching refs:pull
10 as reviewers in pull requests, so that patches may be approved and merged
11 to Zephyr's main branch as part of the original pull requests. The authors
12 of the pull requests are responsible for amending their original commits
16 included in pull requests that are submitted by other Zephyr contributors.
20 own pull requests in order to:
22 * integrate useful content which is part of a stale pull request, or
26 * a developer pushes to a branch or pull request opened by another
29 * assist in updating pull requests in order to get the patches merged
31 * drive stale pull requests to completion so they can be merged
40 * clarify in their pull request the reason for cherry-picking the patches,
42 pull request, and
43 * invite the original author of the patches to their pull request review.
45 A developer who intends to force-push to a branch or pull request of
46 another Zephyr contributor shall clarify in the pull request the reason
48 is done to drive the pull request review to completion, when the pull
52 Developers should try to limit the above practice to pull requests identified
53 as *stale*. Read about how to identify pull requests as stale in
70 inside their original branch or pull request, by other Zephyr developers.