Lines Matching full:github

4 LLVM GitHub User Guide
9 The LLVM Project uses `GitHub <https://github.com/>`_ for
10 `Source Code <https://github.com/llvm/llvm-project>`_,
11 `Releases <https://github.com/llvm/llvm-project/releases>`_,
12 `Issue Tracking <https://github.com/llvm/llvm-project/issues>`_., and
13 `Code Reviews <https://github.com/llvm/llvm-project/pulls>`_.
16 participate in the project using GitHub.
45 The LLVM project is using GitHub Pull Requests for Code Reviews. This document
47 and accepted. This is meant as an overview of the GitHub workflow, for complete
48 documentation refer to `GitHub's documentation <https://docs.github.com/pull-requests>`_.
53    add the `skip-precommit-approval <https://github.com/llvm/llvm-project/labels?q=skip-precommit-approval>`_
56 GitHub Tools
58 You can interact with GitHub in several ways: via git command line tools,
59 the web browser, `GitHub Desktop <https://desktop.github.com/>`_, or the
60 `GitHub CLI <https://cli.github.com>`_. This guide will cover the git command line
61 tools and the GitHub CLI. The GitHub CLI (`gh`) will be most like the `arc` workflow and
74 to your `fork <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks>`_
76 `create a pull request from the fork <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork>`_.
77 As GitHub uses the first line of the commit message truncated to 72 characters
81 Creating Pull Requests with GitHub CLI
94   When you let the GitHub CLI create a fork of llvm-project to
105 your branch instead of force pushing. This makes it easier for GitHub to
112 You can do this manually with an interactive git rebase or with GitHub's
153 GitHub's web interface will be disabled. If this is the case, continue following
158 GitHub's web interface.
164 * Use the button `Squash and merge` in GitHub's web interface, if you do this
174   the merge button in GitHub's web interface afterwards.
176 * Merge using the GitHub command line interface. Switch to your branch locally
213   to a branch in your fork, this is ok and expected. Github's UI for the pull
232 but this is just an artifact of GitHub infrastructure and not a policy of the
262 tools, but the process is a bit more complicated. See GitHub's
263 `documentation <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally?platform=linux&tool=webui#modifying-an-inactive-pull-request-locally>`_
266 Example Pull Request with GitHub CLI
268 Here is an example for creating a Pull Request with the GitHub CLI:
321   git remote add upstream https://github.com/llvm/llvm-project.git
344 Instead of using the GitHub CLI to create a PR, you can push your code to a
345 remote branch on your fork and create the PR to upstream using the GitHub web
348 Here is an example of making a PR using git and the GitHub web interface:
350 First follow the instructions to [fork the repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo?tool=webui#forking-a-repository).
352 Next follow the instructions to [clone your forked repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo?tool=webui#cloning-your-forked-repository).
416   git remote add upstream https://github.com/llvm/llvm-project.git
428 Merge` on your PR in the GitHub web interface.
464 `a Github issue <https://github.com/llvm/llvm-project/issues/new>`_ and using the ``infrastructure`` label.