Lines Matching full:change
22 submitting a change or an enhancement to any Zephyr component, a developer
57 - An author of a change can suggest in his pull-request which category a change
59 changes can change the label of a pull request by adding a comment justifying
60 why a change should belong to another category.
70 Any change that is a fix to an issue that blocks developers from doing their
83 involvement. Such changes should not change the logic or the design of a
84 subsystem or component. For example a trivial change can be:
112 Changes that introduce new features or functionality or change the way the
116 stakeholders are made aware of the change.
140 when reviewers are not available and there is a need to get a code change into
146 Any change requests (-1) on a pull request have to be justified. A reviewer
148 that a change should not be merged without their review, then: Request change
177 - The review is unrelated to the code change or asking for unjustified
192 to questions and provide clarifications regarding the issue or the change.
315 The issue or PR describes a change to a stable API.
388 * - :guilabel:`Breaking API Change`
389 - The issue or PR describes a breaking change to a stable API. See additional information