Lines Matching full:changes

122 Changes to the main branch of a module repository, including synchronization
126 ensures that the incoming changes are always **reviewable**, and the
130 changes that are to be brought into the module repository.
146 Upstream changes brought as a single *snapshot* commit (manual diff) in a
162 Upstream changes brought in by performing a Git merge of the intended upstream
229 * the contributor of the original changes in Zephyr is required to submit
230   the corresponding changes that are required in module repositories, to
231   ensure that Zephyr CI on the pull request with the original changes, as
244 Contributing changes to modules
247 Submitting and merging changes directly to a module's codebase, that is,
251 * changes required due to updates in the zephyr main tree
252 * urgent changes that should not wait to be merged in the external project
255 Non-trivial changes to a module's codebase, including changes in the module
257 project repository. In that case, such changes shall be submitted to the
260 :ref:`Submitting changes to modules <submitting_new_modules>` describes in
261 detail the process of contributing changes to module repositories.
271 repositories may only be merged if the introduced changes are verified
369   twister runs in pull requests that introduce changes in module
396 * Licensing changes in the external project
1052 Submitting changes to modules
1055 When submitting new or making changes to existing modules the main repository
1056 Zephyr needs a reference to the changes to be able to verify the changes. In the
1060 allow building the zephyr main tree with the changes submitted to the
1063 To avoid merging changes to master with pull request information, the pull
1070 maintainer to the commit hash of the module which reflects the changes.
1072 Note that multiple and dependent changes to different modules can be submitted
1090 module related files and changes in relation to upstream need to be maintained
1116 *my_module* repository. Once the module changes are reviewed and merged, the
1121 Process for submitting changes to existing modules
1124 #. Submit the changes using a pull request to an existing repository following
1147 *my_module* repository. Once the module changes are reviewed and merged, the