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

Conflicts:
	db/schema.rb

Hide ldap group links if ldap is not enabled

This MR also includes a fix for next issue: prevent 500 error on ldap group links page if group has links to ldap servers that are disabled or removed from gitlab config.

Fixes #196

See merge request !264

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

Dropdown icon not clickable

Fixes #1642 by using `pointer-events` property supported by [modern browsers](http://caniuse.com/#search=pointer-events)

See merge request !1319

Show files named diff

Fixes #1749

See merge request !1318

Add an extra reference to the 'shell commands' guide

The 'shell commands' guide now also has tips on opening/reading files and handling paths.

See merge request !1321

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

Enable Markdown preview for issues, merge requests, milestones, and notes

Add security tips about file and paths

These are some extra guidelines to guard against code execution and path traversal.

See merge request !1317

Updated doc/integration/twitter.md, fixed incorrect callback URL

Fixed a typo in the Integration instructions for Twitter OAuth

See merge request !257

(referencing /users/auth/github/callback,
 not /users/auth/twitter/callback)

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

Speed up omniauth AddIdentityTable migration

https://dev.gitlab.org/gitlab/gitlabhq/issues/1810

See merge request !1315

If group has links to ldap servers that are disabled or removed from
gitlab config.
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Unicorn workers

See merge request !1316

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

Unicorn advice

See merge request !1314

Add 'grace time' behavior to Sidekiq MemoryKiller

The previous iteration of the memory killer did not give 'large'
jobs much of a chance to finish. This caused them to come back after
each restart, leading to another memory-induced shutdown. By adding
some 'grace time' between the moment we detect a memory peak and
the moment we start shutting down, we hope to give Sidekiq a chance
to get whatever causes its memory to grow 'out of its system'.

See merge request !1313

Upstream changes from CE

See merge request !262

Drop vagrant from issue tracker guidelines

Is this the preferred method of reproducing an issue? If yes, disregard this MR.

\cc @sytses @marin

See merge request !255

Move sidekiq debug docs to development folder

Conflicts:
	spec/routing/project_routing_spec.rb