Lines Matching refs:will
12 and enhancement requests, and submit patches to the project so your patch will
147 author the commit (CI will fail if there is no match)
173 * the content of the patches will not be substantially modified,
201 tools yourself, you will need to rely on the Continuous Integration (CI)
330 triage team will review and comment on the submission, typically within a few
357 address you use to sign your commits. If they don't match, the CI system will
452 pull request will fail CI checks if you do not.
455 it's needed. Be specific. A body that says ``"Fixes stuff"`` will be
618 you are a Linux user, ``clang-format`` will likely be available as a package in
646 of the run you will see:
654 Once you click on the link you will be taken to the ``Github actions`` summary
655 results page where a table with all the different builds will be shown. To see
725 tools. These issues will have the same (or equivalent) priority initially
746 closed without a fix or without ignoring the entry in the scan service will be
832 message. Your commit will be rejected without this line that indicates your
849 #. A bot will assign one or more suggested reviewers (based on the
854 review. Email will be sent as review comments are made, or you can check
857 .. note:: As more commits are merged upstream, the GitHub PR page will show
860 as the commits will be rebased as part of merging anyway, and triggering
861 a branch update from the GitHub UI will cause the PR approvals to be
893 By force pushing your update, your original pull request will be updated
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
928 attention needed and it will be ready for merge sooner than later:
967 can be discussed. This will also allow us to better coordinate our efforts,
970 will increase the chances of your issue being dealt with quickly:
1059 must include the issue on the agenda and discuss whether the project will