Lines Matching +full:merge +full:- +full:pr

51   (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
54 ….github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permiss…
102 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
107 approvals needed to merge a PR. Other criteria for merging may apply.
141 required approvals needed to merge a PR. Other criteria for merging may apply.
171   :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews
175 * Responsibility to re-assign a pull request if they are the original submitter
200 .. _release-engineering-team:
215 * Right to merge code changes to the zephyr tree following the project rules.
220 * Responsibility to merge all contributions regardless of their
222   maintainers and follow the merge criteria of a change.
237   time-zones).
254 …stone (M3, see `program management overview <https://wiki.zephyrproject.org/Program-Management>`_.)
273 …   ..             ..               **Admin**  **Merge Rights**   Member      Owner     Collaborator
274 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
276 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
278 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
299   * Un-maintained areas should be indicated clearly in the MAINTAINERS file
304   * Parent-area maintainer should be acting as default substitute/fallback
305     assignee for un-maintained sub-areas
306   * Area maintainer gets precedence over parent-area maintainer
308 * Pull requests may be re-assigned if this is needed or more appropriate
310   * Re-assigned by original assignee
324 * Architectures, core components, sub-systems, samples, tests
329   * May have a maintainer, shall have a higher-level platform maintainer
332   * Shall have a driver-area (and API) maintainer
335   * In the above case, platform-specific PRs may be
336     re-assigned to respective collaborator/contributor of driver
350 Merge Criteria
362   approvals, the merge criteria is extended with the guidelines below:
378   * Release engineers shall not merge code changes originating and reviewed
379     only by their own organisation. To be able to merge such changes, at least