Lines Matching full:your
12 and enhancement requests, and submit patches to the project so your patch will
32 allows you to freely use, modify, distribute and sell your own products
139 Signed-off-by: Your Name <your.email@example.com>
141 For your commits, replace:
143 - ``Your Name`` with your legal name (pseudonyms, hacker handles, and the
146 - ``your.email@example.com`` with the same email address you are using to
149 You can automatically add the Signed-off-by: line to your commit body using
157 your Signed-off-by: line without removing the existing one.
159 - If you forget to add the Signed-off-by: line, you can add it to your previous
162 - If you've pushed your changes to GitHub already you'll need to force push
163 your branch after this with ``git push -f``.
188 and how to set up your development environment as introduced in the Zephyr
195 on https://github.com and have Git tools available on your development system.
203 your Pull Request (PR). You can see any failure results in the workflow
322 Server`_) to see what others think of your issue (and proposed solution). You
325 mailing list`_ to introduce and discuss your idea with the development
329 submitting your own. When you submit an issue (bug or feature request), the
342 information to your Git installation, set the Git configuration
343 variables ``user.name`` to your full name, and ``user.email`` to your
346 For example, if your name is ``Zephyr Developer`` and your email
355 ``user.name`` must be your full name (first and last at minimum), not a
356 …pseudonym or hacker handle. The email address that you use in your Git configuration must match th…
357 address you use to sign your commits. If they don't match, the CI system will
358 fail your pull request.
360 If you intend to edit commits using the Github.com UI, ensure that your github profile
361 ``email address`` and profile ``name`` also match those used in your git configuration
388 Signed-off-by: [Your Full Name] <[your.email@address]>
391 fit your commit.
451 changes, please include a descriptive commit message body. Your
454 This part of the commit should explain what your change does, and why
463 Each line in your commit message should usually be 75 characters or
476 You should have set your :ref:`git_setup`
477 already. Create your commit with ``git commit -s`` to add the
480 For open source licensing reasons, your commit must include a
485 Signed-off-by: [Your Full Name] <[your.email@address]>
487 For example, if your full name is ``Zephyr Developer`` and your email
494 This means that you have personally made sure your change complies
495 with the :ref:`DCO`. For this reason, you must use your legal name.
498 Your name and the email address you use must match the name and email
557 Use these coding guidelines to ensure that your development complies with the
619 your distribution repositories.
688 If you think your change may break some test, you can submit your PR as a draft
741 "Intentional", the action to "Ignore", owner to your own account and add a
759 information as you can about your change, update appropriate documentation,
760 and test your changes thoroughly before submitting.
771 to your personal account on GitHub. (Click on the fork button in the top
774 #. On your development computer, change into the :file:`zephyr` folder that was
787 git remote add origin https://github.com/<your github id>/zephyr
795 origin https://github.com/<your github id>/zephyr (fetch)
796 origin https://github.com/<your github id>/zephyr (push)
800 #. Create a topic branch (off of ``main``) for your work (if you're addressing
807 ``main`` so you may need to indicate this in your checkout::
814 #. When things look good, start the pull request process by adding your changed
827 #. Commit your changes to your local repo::
831 The ``-s`` option automatically adds your ``Signed-off-by:`` to your commit
832 message. Your commit will be rejected without this line that indicates your
834 specific guidelines for writing your commit messages.
836 #. Push your topic branch with your changes to your fork in your personal
841 #. In your web browser, go to your forked repo and click on the
846 request for the ``main`` branch. The title and message from your commit
853 #. Click on the submit button and your pull request is sent and awaits
855 on your pull request at https://github.com/zephyrproject-rtos/zephyr/pulls.
864 #. While you're waiting for your pull request to be accepted and merged, you
865 can create another branch to work on another issue. (Be sure to make your
873 #. If reviewers do request changes to your patch, you can interactively rebase
874 commit(s) to fix review issues. In your development repo::
879 a specific commit (if there's more than one in your pull request), or
883 As before, inspect and test your changes. When ready, continue the
893 By force pushing your update, your original pull request will be updated
894 with your changes so you won't need to resubmit the pull request.
897 merge conflict. If so, rebase your local branch::
916 #. If the CI run fails, you will need to make changes to your code in order
917 to fix the issues and amend your commits by rebasing as described above.
927 Pull Requests. If you follow them, chances are your pull request will get the
941 #. Make sure your PR has a body with more details about the content of your
963 proposal (RFC) for your work first, to be sure that we can use it. Please
966 * For a Major Feature, first open an issue and outline your proposal so that it
970 will increase the chances of your issue being dealt with quickly: