summaryrefslogtreecommitdiff
path: root/doc/api/commits.md
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axilleas@axilleas.me>2016-08-01 06:56:16 +0000
committerAchilleas Pipinellis <axilleas@axilleas.me>2016-08-01 06:56:16 +0000
commit2f344eca42f1f0fa8ac122316687bc166c489bf1 (patch)
treebd9fe267cb1db6551e786042abfc4b9170abc3cd /doc/api/commits.md
parentdc775b0a9131cea6be5ae6b0ec3fba662af26b42 (diff)
parentdc7805cd999dc6c97c407cbb419d1bb1cc36a71f (diff)
downloadgitlab-ce-2f344eca42f1f0fa8ac122316687bc166c489bf1.tar.gz
Merge branch 'master' into 'master'
Update start-using-git.md to reflect that merges to master can be made from either the master or the named branch. ## What does this MR do? The documentation is incorrect in stating that you need to be in the named branch in order to merge to master. You can be in master and merge the named branch, too. ## Are there points in the code the reviewer needs to double check? Yes ## Why was this MR needed? This MR is needed to correct an inaccuracy in the documentation. ## What are the relevant issue numbers? N/A ## Screenshots (if relevant) N/A ## Does this MR meet the acceptance criteria? It is only a documentation change, so mostly this is not applicable. - [ ] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - [ ] API support added - Tests - [ ] Added for this feature/bug - [ ] All builds are passing - [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [ ] Branch has no merge conflicts with `master` (if you do - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !5404
Diffstat (limited to 'doc/api/commits.md')
0 files changed, 0 insertions, 0 deletions