Lines Matching refs:changes
36 changes are proposed using pull request, we need to allow for a minimal review
38 on changes. There are different categories of changes and we know that some
39 changes do require reviews by subject matter experts and owners of the subsystem
40 being changed. Many changes fall under the "trivial" category that can be
42 code-owner review. Additionally, some changes might require further discussions
59 changes can change the label of a pull request by adding a comment justifying
82 Trivial changes are those that appear obvious enough and do not require maintainer or code-owner
83 involvement. Such changes should not change the logic or the design of a
86 - Documentation changes
87 - Configuration changes
90 - Test changes and fixes
96 Any changes that touch the logic or the original design of a subsystem or
98 maintainer. If the code changes is initiated by a contributor or developer other
114 Group. For example for :ref:`breaking API changes <breaking_api_changes>`, the
136 - Release related changes: Changing version file, applying tags and release
137 related activities without any code changes.
168 If a reviewer has requested changes in a pull request, he or she should monitor
178 structural changes such as:
201 All changes submitted to GitHub are subject to tests that are run on
204 of all boards and platforms. Documentation changes are also verified
327 - Simple changes that can have shorter review time and be reviewed by anyone, i.e. typos,