User-search

Deploy-key-doc-improvement

Link-to-doc-site

Hyphens-in-doc-filename

Pagination-link-header-doc

Typo-in-docs

Refactor branches API

Preparing for new feature: Create branches via API

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Grammar correction: "View in Gitlab"

add 'Link' header for API response

Configurable repo downloads path

Changed to "View on Gitlab"

Refactor project watchers notifications

Fix searching by extern_uid for LDAP to be case-insensitive

.well-list item name spacing fix Follow up on #6643

Conflicts:
	CHANGELOG

Remove omniauth-ldap nickname bug workaround

Before there was a bug in omniauth-ldap which prevented samaccountname
showing up as a possible username for new LDAP users. Thanks to upstream
fixes, we no longer need to work around this bug.

Invoking 'db:schema:load' turned out to be a bad idea: when downgrading
an existing GitLab installation, the schema of the newer version would
be preserved when trying to import the old version.

Pages affected:
- admin/groups#show
- admin/projets#index
- admin/users#index
- dashboard/issues#index (on small screens)

Update Contribution Guidelines: Specify Merge Request To Master

There have been occasions where contributors submitted merge requests to stable branches thinking that was the way to get changes into specific releases. This results in wasted time and effort of the GitLab team responding to the merge request requesting that it be to master, as well as the developer who needs to redo the changes.

This merge request very simply updates the contribution guidelines to specify that MRs should only be to master, and that getting changes into stable branches will be determined by the GitLab Team.

cc @JobV

Update 6.0-to-6.5.md

Getting-help-on-website

Doc-readme-for-site

New readme files for doc.gitlab.com
I also but the links for the api readme at the top.

Fix another instance of "created at"