Lines Matching +full:- +full:- +full:coverage +full:- +full:tool

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…
112 not follow the :ref:`expectations <reviewer-expectations>` and the guidelines
181   :ref:`expectations <reviewer-expectations>` from reviewers and seek reviews
185 * Responsibility to re-assign a pull request if they are the original submitter
198 * Right to revert any triage in a static analysis tool (e.g: Coverity)
210 .. _release-engineering-team:
247   time-zones).
264 …stone (M3, see `program management overview <https://wiki.zephyrproject.org/Program-Management>`_.)
284 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
286 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
288 …---------------- ------------------- ----------- ---------------- ----------- ----------- --------…
309   * Un-maintained areas should be indicated clearly in the MAINTAINERS file
314   * Parent-area maintainer should be acting as default substitute/fallback
315     assignee for un-maintained sub-areas
316   * Area maintainer gets precedence over parent-area maintainer
318 * Pull requests may be re-assigned if this is needed or more appropriate
320   * Re-assigned by original assignee
334 * Architectures, core components, sub-systems, samples, tests
339   * May have a maintainer, shall have a higher-level platform maintainer
342   * Shall have a driver-area (and API) maintainer
345   * In the above case, platform-specific PRs may be
346     re-assigned to respective collaborator/contributor of driver
412   * Code coverage
415   * Documentation coverage (APIs)