Lines Matching full:you
30 contribution and allowing you to use the software however you would like
32 allows you to freely use, modify, distribute and sell your own products
43 A license tells you what rights you have as a developer, as provided by 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
156 - If you are altering an existing commit created by someone else, you must add
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
186 As a contributor, you'll want to be familiar with the Zephyr project, how to
191 You should be familiar with common developer tools such as Git and CMake, and
194 If you haven't already done so, you'll need to create a (free) GitHub account
201 tools yourself, you will need to rely on the Continuous Integration (CI)
202 service using Github Actions, which runs automatically on GitHub when you submit
203 your Pull Request (PR). You can see any failure results in the workflow
216 Zephyr kernel itself, you'll also find the sources for technical documentation,
320 system to see what's been reported on the issue you'd like to address. Have a
322 Server`_) to see what others think of your issue (and proposed solution). You
323 may find others that have encountered the issue you're finding, or that have
329 submitting your own. When you submit an issue (bug or feature request), the
333 You can find all `open pull requests`_ on GitHub and open `Zephyr Project
341 We need to know who you are, and how to contact you. To add this
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
360 If you intend to edit commits using the Github.com UI, ensure that your github profile
371 similar to the ones you are proposing.
390 You need to change text in square brackets (``[like this]``) above to
434 If you're not sure what to use, try running ``git log FILE``, where
435 ``FILE`` is a file you are changing, and using previous commits that
440 what you've done. Here are some examples:
452 pull request will fail CI checks if you do not.
459 * **why** you chose that approach,
461 * **how** you know it works -- for example, which tests you ran.
467 For examples of accepted commit messages, you can refer to the Zephyr GitHub
476 You should have set your :ref:`git_setup`
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
526 You can point to other relevant information that can be found on the web using
576 Instead of running checkpatch at each commit, you may prefer to run it only
598 If you want to override checkpatch verdict and push you branch despite reported
599 issues, you can add option --no-verify to the git push command.
610 editors, but you can also run it manually like this:
618 you are a Linux user, ``clang-format`` will likely be available as a package in
646 of the run you will see:
651 In case of failure you can click on the "Details" link presented below the
654 Once you click on the link you will be taken to the ``Github actions`` summary
688 If you think your change may break some test, you can submit your PR as a draft
689 and let the project CI automatically run the :ref:`twister_script` for you.
691 If a test fails, you can check from the CI run logs how to rerun it locally,
719 results you have to create an account yourself. From the Zephyr project page,
720 you may select "Add me to project" to be added to the project. New members must
758 When contributing to the Zephyr Project, it is also important you provide as much
759 information as you can about your change, update appropriate documentation,
775 created when you :ref:`obtained the code <get_the_code>`::
785 Let Git know about the fork you just created, naming it ``origin``::
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::
817 git add [file(s) that changed, add -p if you want to be more specific]
819 You can see files that are not yet staged using::
823 #. Verify changes to be committed look as you expected::
842 ``Compare & pull request`` button for the branch you just worked on and
843 you want to open a pull request with.
845 #. Review the pull request changes, and verify that you are opening a pull
850 MAINTAINERS file in the repo). If you are a project member, you can
854 review. Email will be sent as review comments are made, or you can check
864 #. While you're waiting for your pull request to be accepted and merged, you
873 #. If reviewers do request changes to your patch, you can interactively rebase
894 with your changes so you won't need to resubmit the pull request.
911 one - GitHub complains it can't find older commits. You're also not
916 #. If the CI run fails, you will need to make changes to your code in order
927 Pull Requests. If you follow them, chances are your pull request will get the
944 #. Make sure you reference the issue you are fixing in the body of the PR
952 #. If you get request for changes and submit a change to address them, make
953 sure you click the "Re-request review" button on the GitHub UI to notify
960 You can request a new feature or submit a proposal by submitting an issue to
962 If you would like to implement a new feature, please submit an issue with a
968 prevent duplication of work, and help you to craft the change so that it is