Lines Matching full:changes

8 standards and methods for submitting changes help reduce the chaos that can result
160 - If you've pushed your changes to GitHub already you'll need to force push
322 similar ideas for changes or additions.  Send a message to the `Zephyr devel
384 To verify that your changes did not break any tests or samples, please run the
415 In case of major changes to the kernel, build or configuration infrastructures
416 of Zephyr, it is advised to use twister for verifying majority the changes
559 controlled changes. This practice simplifies review, makes merging and
564 and test your changes thoroughly before submitting.
615 #. Make changes, test locally, change, test, test again, ...  (Check out the
627 #. Verify changes to be committed look as you expected::
631 #. Commit your changes to your local repo::
640 #. Push your topic branch with your changes to your fork in your personal
649 #. Review the pull request changes, and verify that you are opening a pull
677 #. If reviewers do request changes to your patch, you can interactively rebase
693    As before, inspect and test your changes. When ready, continue the
704    with your changes so you won't need to resubmit the pull request.
709       such as not being able to use "View Changes" buttons except for the last
715 #. If the CI run fails, you will need to make changes to your code in order
725 Changes are submitted as Git commits. Each commit has a *commit
774   * ``doc: ...`` for documentation changes
775   * ``drivers: foo:`` for ``foo`` driver changes
776   * ``Bluetooth: Shell:`` for changes to the Bluetooth shell
777   * ``net: ethernet:`` for Ethernet-related networking changes
778   * ``dts:`` for treewide devicetree changes
779   * ``style:`` for code style changes
798    changes, please include a descriptive commit message body. Your
931 * Documentation build to verify any doc changes
958 submitting changes to :ref:`existing modules <changes_to_existing_module>`.
960 .. _treewide-changes:
962 Treewide Changes
965 This section describes contributions that are treewide changes and some
967 to try to give such changes increased review and user visibility due to their
974 or other development requirements that either implies required changes
987 Requirements for Treewide Changes  argument
991   pull requests that are treewide changes
1016 Some example past treewide changes are:
1027 such APIs, however, are treewide changes.