summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorJim Lin <tclin914@gmail.com>2020-01-08 09:48:01 +0800
committerJim Lin <tclin914@gmail.com>2020-01-08 09:48:01 +0800
commitf90a2c2d2cdb679cb38400408ac5e26bea65fd14 (patch)
treeb403cc162d7e9d780e7409a3c674995bd3979928 /llvm/docs
parent9de6a3987251d05eb734e34597dcde2f12aac9ba (diff)
downloadbcm5719-llvm-f90a2c2d2cdb679cb38400408ac5e26bea65fd14.tar.gz
bcm5719-llvm-f90a2c2d2cdb679cb38400408ac5e26bea65fd14.zip
[docs] Improve HowTo commit changes from git
Summary: As a novice here I tried to `git push` my changes for a while before figuring out the correct workflow which is described on other pages. This small change doesn't reduce redundancy between those pages, but at least readers can follow the links now. Reviewers: Kokan, Jim Reviewed By: Kokan, Jim Subscribers: riccibruno, kiszk, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D72077
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/GettingStarted.rst6
1 files changed, 5 insertions, 1 deletions
diff --git a/llvm/docs/GettingStarted.rst b/llvm/docs/GettingStarted.rst
index 086ae80d4b1..6dfca656d43 100644
--- a/llvm/docs/GettingStarted.rst
+++ b/llvm/docs/GettingStarted.rst
@@ -491,7 +491,11 @@ For developers to commit changes from Git
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Once a patch is reviewed, you should rebase it, re-test locally, and commit the
-changes to LLVM's master branch. This is done using `git push`.
+changes to LLVM's master branch. This is done using `git push` if you have the
+required access rights. See `committing a change
+<Phabricator.html#committing-a-change>`_ for Phabricator based commits or
+`Developer Policy <DeveloperPolicy.html#obtaining-commit-access>`_ for commit
+access.
LLVM currently has a linear-history policy, which means that merge commits are
not allowed. The `llvm-project` repo on github is configured to reject pushes
OpenPOWER on IntegriCloud