[docs] Improve HowTo commit changes from git

[AlexanderLanin]

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.

[kiszk]

llvm/docs/GettingStarted.rst

495

nit: comitting -> committing

[AlexanderLanin]

Hups, thanks.

I do not have commit rights to the repository, someone please commit this change.
Alexander Lanin <[e-mail]>

[AlexanderLanin]

ping? Could someone push this please.

[Jim]

Sorry about that I forgot to modify author information.

llvm/docs/GettingStarted.rst

 
 
 .. _commit_from_git:
 
 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
 that include merges, so the `git rebase` step above is required.
 
 Reverting a change
 ^^^^^^^^^^^^^^^^^^