Lines Matching refs:changes

8 standards and methods for submitting changes help reduce the chaos that can result
162 - If you've pushed your changes to GitHub already you'll need to force push
324 similar ideas for changes or additions.  Send a message to the `Zephyr devel
370 repository. Use the search filters and labels to locate PRs related to changes
427   * ``doc: ...`` for documentation changes
428   * ``drivers: foo:`` for ``foo`` driver changes
429   * ``Bluetooth: Shell:`` for changes to the Bluetooth shell
430   * ``net: ethernet:`` for Ethernet-related networking changes
431   * ``dts:`` for treewide devicetree changes
432   * ``style:`` for code style changes
451    changes, please include a descriptive commit message body. Your
637 * Documentation build to verify any doc changes
674 Developers are encouraged to run the script locally to validate their changes
755 controlled changes. This practice simplifies review, makes merging and
760 and test your changes thoroughly before submitting.
811 #. Make changes, test locally, change, test, test again, ...  (Check out the
823 #. Verify changes to be committed look as you expected::
827 #. Commit your changes to your local repo::
836 #. Push your topic branch with your changes to your fork in your personal
845 #. Review the pull request changes, and verify that you are opening a pull
873 #. If reviewers do request changes to your patch, you can interactively rebase
883    As before, inspect and test your changes. When ready, continue the
894    with your changes so you won't need to resubmit the pull request.
916 #. If the CI run fails, you will need to make changes to your code in order
933 #. When pushing follow-up changes, use the ``--keep-base`` option of
952 #. If you get request for changes and submit a change to address them, make
954    those who asked for the changes
1017 submitting changes to :ref:`existing modules <changes_to_existing_module>`.
1019 .. _treewide-changes:
1024 This section describes contributions that are treewide changes and some
1026 to try to give such changes increased review and user visibility due to their
1033 or other development requirements that either implies required changes
1050   pull requests that are treewide changes
1075 Some example past treewide changes are:
1086 such APIs, however, are treewide changes.