Lines Matching +full:pull +full:- +full:requests

21 -----------
27 ---------
36 a debug build (`-DCMAKE_BUILD_TYPE=Debug`) or a build with assertions
37 (`-DLLVM_ENABLE_ASSERTIONS=On`, enabled for Debug builds).
40 --------------------------
42 There is a separate process to submit security-related bugs, see :ref:`report-security-issue`.
45 ---------------------
58 * conform to the :doc:`CodingStandards`. You can use the `clang-format-diff.py`_ or `git-clang-format`_ tools to automatically format your patch properly.
61 * have a single commit, up-to-date with the upstream ``origin/main`` branch, and don't have merges.
66 formatted properly. We use ``clang-format`` for this, which has git integration
67 through the ``git-clang-format`` script. On some systems, it may already be
69 run it -- the following command will format only the code changed in the most
72 .. code-block:: console
74   % git clang-format HEAD~1
76 Note that this modifies the files, but doesn't commit them -- you'll likely want
79 .. code-block:: console
81   % git commit --amend -a
86   If you don't already have ``clang-format`` or ``git clang-format`` installed
87   on your system, the ``clang-format`` binary will be built alongside clang, and
89   ``clang/tools/clang-format/git-clang-format``.
91 The LLVM project has migrated to GitHub Pull Requests as its review process.
92 For more information about the workflow of using GitHub Pull Requests see our
93 :ref:`GitHub <github-reviews>` documentation. We still have an read-only
102 sub-directory. For example, LLVM's is ``llvm/Maintainers.md`` and Clang's is
107 them in a comment -- just @name them.
119   * You have set a valid email address in your GitHub account, see :ref:`github-email-address`.
125 For more information on LLVM's code-review process, please see
131 -----------------------------------------
136 When pushing directly from the command-line to the ``main`` branch, you will need
137 to rebase your change. LLVM has a linear-history policy, which means
143 .. code-block:: console
147   remote: - Required status check “buildkite/github-pull-requests” is expected.
150 intended as a warning for people merging pull-requests with failing CI. We can't
151 disable it for people pushing on the command-line.
157 Git pre-push hook
160 We include an optional pre-push hook that run some sanity checks on the revisions
164 .. code-block:: console
166   % ln -sf ../../llvm/utils/git/pre-push.py .git/hooks/pre-push
172 of LLVM's high-level design, as well as its internals:
201 .. _good first issue: https://github.com/llvm/llvm-project/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
202 .. _bug tracker: https://github.com/llvm/llvm-project/issues
203 .. _clang-format-diff.py: https://github.com/llvm/llvm-project/blob/main/clang/tools/clang-format/clang-format-diff.py
204 .. _git-clang-format: https://github.com/llvm/llvm-project/blob/main/clang/tools/clang-format/git-clang-format
205 .. _LLVM's GitHub: https://github.com/llvm/llvm-project
206 .. _LLVM's Phabricator (read-only): https://reviews.llvm.org/