Lines Matching full:you
21 As a contributor, you'll want to be familiar with the Zephyr project, how to
26 You should be familiar with common developer tools such as Git and CMake, and
29 If you haven't already done so, you'll need to create a (free) GitHub account
36 tools yourself, you will need to rely on the Continuous Integration (CI)
37 service using Github Actions, which runs automatically on GitHub when you submit
38 your Pull Request (PR). You can see any failure results in the workflow
58 contribution and allowing you to use the software however you would like
60 allows you to freely use, modify, distribute and sell your own products
71 A license tells you what rights you have as a developer, as provided by the
179 - ``your.email@example.com`` with the same email address you are using to
182 You can automatically add the Signed-off-by: line to your commit body using
189 - If you are altering an existing commit created by someone else, you must add
201 Zephyr kernel itself, you'll also find the sources for technical documentation,
305 system to see what's been reported on the issue you'd like to address. Have a
307 Server`_) to see what others think of your issue (and proposed solution). You
308 may find others that have encountered the issue you're finding, or that have
314 submitting your own. When you submit an issue (bug or feature request), the
318 You can find all `open pull requests`_ on GitHub and open `Zephyr Project
326 We need to know who you are, and how to contact you. To add this
341 …pseudonym or hacker handle. The email address that you use in your Git configuration must match th…
342 address you use to sign your commits. If they don't match, the CI system will
345 If you intend to edit commits using the Github.com UI, ensure that your github profile
356 similar to the ones you are proposing.
375 You need to change text in square brackets (``[like this]``) above to
414 If you're not sure what to use, try running ``git log FILE``, where
415 ``FILE`` is a file you are changing, and using previous commits that
420 what you've done. Here are some examples:
432 pull request will fail CI checks if you do not.
439 * **why** you chose that approach,
441 * **how** you know it works -- for example, which tests you ran.
447 For examples of accepted commit messages, you can refer to the Zephyr GitHub
456 You should have set your :ref:`git_setup`
474 This means that you have personally made sure your change complies
475 with the :ref:`DCO`. For this reason, you must use your legal name.
478 Your name and the email address you use must match the name and email
506 You can point to other relevant information that can be found on the web using
534 of the run you will see:
539 In case of failure you can click on the "Details" link presented below the
542 Once you click on the link you will be taken to the ``Github actions`` summary
583 If you think your change may break some test, you can submit your PR as a draft
584 and let the project CI automatically run the :ref:`twister_script` for you.
586 If a test fails, you can check from the CI run logs how to rerun it locally,
614 results you have to create an account yourself. From the Zephyr project page,
615 you may select "Add me to project" to be added to the project. New members must
653 When contributing to the Zephyr Project, it is also important you provide as much
654 information as you can about your change, update appropriate documentation,
670 created when you :ref:`obtained the code <get_the_code>`::
680 Let Git know about the fork you just created, naming it ``origin``::
695 #. Create a topic branch (off of ``main``) for your work (if you're addressing
702 ``main`` so you may need to indicate this in your checkout::
712 git add [file(s) that changed, add -p if you want to be more specific]
714 You can see files that are not yet staged using::
718 #. Verify changes to be committed look as you expected::
737 ``Compare & pull request`` button for the branch you just worked on and
738 you want to open a pull request with.
740 #. Review the pull request changes, and verify that you are opening a pull
745 MAINTAINERS file in the repo). If you are a project member, you can
749 review. Email will be sent as review comments are made, or you can check
752 #. While you're waiting for your pull request to be accepted and merged, you
761 #. If reviewers do request changes to your patch, you can interactively rebase
782 with your changes so you won't need to resubmit the pull request.
799 one - GitHub complains it can't find older commits. You're also not
804 #. If the CI run fails, you will need to make changes to your code in order
815 Pull Requests. If you follow them, chances are your pull request will get the
832 #. Make sure you reference the issue you are fixing in the body of the PR
840 #. If you get request for changes and submit a change to address them, make
841 sure you click the "Re-request review" button on the GitHub UI to notify