Lines Matching refs:changes
7 changes as smaller pull requests. Smaller pull requests (PRs) have the following
11 to set aside a few minutes to review smaller changes several times than it is
18 changes in the tree.
42 - Modifying a feature, especially for API behavior contract changes.
62 the PR into multiple commits targeting these specific changes:
74 Large changes to the Zephyr project must submit an :ref:`RFC proposal <rfcs>`
84 - :ref:`treewide-changes`.
85 - Other large changes that can benefit from the RFC proposal process.
96 - The PR description must include a summary of the changes and their rationales.
129 - Incompatible changes to APIs must also update the release notes for the
160 with no other changes since the last push of the PR. When pushing a rebase
277 #. PRs where the reviewer has requested blocking changes.
292 - Code style changes that impact the readability of the PR.
293 - Reviewing commits separately when the requested changes cascade into the
304 only non-blocking changes remain. The PR author has discretion as to whether
308 - Reviewers shall be *clear* and *concise* what changes they are requesting when the
309 "Request Changes" option is used. Requested changes shall be in the scope of
314 If requested changes cannot be resolved within the review process, the