Lines Matching +full:stale +full:- +full:pr +full:- +full:message
19 * a developer cherry-picks commits submitted by other contributors into their
22 * integrate useful content which is part of a stale pull request, or
31 * drive stale pull requests to completion so they can be merged
37 A developer who intends to cherry-pick and potentially modify patches sent by
40 * clarify in their pull request the reason for cherry-picking the patches,
45 A developer who intends to force-push to a branch or pull request of
53 as *stale*. Read about how to identify pull requests as stale in
54 :ref:`development processes and tools <dev-environment-and-tools>`
60 the original sign-off line and author identity, or
62 *own* sign-off line and author identity). In this case, the developer
63 shall identify in the commit message(s) the original source the
64 submitted work is based on (mentioning, for example, the original PR