Explain where the memory recommendation comes from

The 250MB repo limit is caused by the git command line.

Also see MR !422

Rename "Website url" labels to "Website"

Encouragement during install

Fix select2 css for drop above style less than a minute ago

Fix 500 error on project issues and merge requests pages

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

Fix assign-to-me link for MergeRequest form

Import Doc

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

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

Git clone performance is still the same

This reverts commit a757c4a2.

While it is true that Grack memory use while sending data to a client
was improved, this does not change the fact that the Git processes
running on a GitLab server will use more memory for large repositories.

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

Add IRC nicknames to channel admins

Add EE checkout instructions to update docs

Better check on the validity of emails

Merge branch 'add_website_url_to_user' of https://github.com/jeromedalbert/gitlabhq into jeromedalbert-add_website_url_to_user
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Conflicts:
	CHANGELOG

Improve: Search autocomplete

* fetch options via ajax
* only show options related to user input
* add limit to amount of options

Update select branch to GitLab look and explain why this guide is long so people are not discouraged.

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

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

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

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

Efficient Clone

Since https://github.com/gitlabhq/grack/pull/1 this warning is no longer needed I think.

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

Improve the explanation of the LDAP check script

Explain allow_username_or_email_login LDAP setting

Refactoring context Into services

To prevent confusion where to write logic. Context or Service?

Feature: base64 encoding for blob content