Fixes gitlab-org/gitlab-ce#15254 gitlab-org/gitlab-ce#14277

[ci skip]

Add Safari search box bug fix to changelog



See merge request !3951

Updated triggers UI

![Screen_Shot_2016-04-27_at_14.05.35](/uploads/971bc907f62abd397368c8c088ff0cf1/Screen_Shot_2016-04-27_at_14.05.35.png)

![Screen_Shot_2016-04-27_at_14.05.32](/uploads/5e0e87998e25e7e89cdd6fb8d6035542/Screen_Shot_2016-04-27_at_14.05.32.png)

Closes #14090

See merge request !3946

Project group UI

Closes #13991 

![Screen_Shot_2016-04-25_at_14.54.49](/uploads/e55fd1731a479d93660a1ff8359f56d6/Screen_Shot_2016-04-25_at_14.54.49.png)

See merge request !3911

Fix Todos test

Another attempt to fix random fail on Todos test.

See merge request !3953

Grey header and fluid profile navigation

Based on https://gitlab.com/gitlab-org/gitlab-ce/issues/14838#note_5083863 

cc @skyruler

See merge request !3968

Replace gitlab-workhorse with GitLab Workhorse where appropriate

For the output to be consistent with the other services.

See merge request !2512

Disable Rack Attack if admin disables it in config file

Grack::Auth already checks this variable. These holdouts were not disabled, leading to confusion when debugging a customer issue.

See merge request !3918

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

Prepend letter v to GitLab Workhorse version numbers

This helps to address gitlab-org/gitlab-ce#12684 so as to maintain consistency in all GitLab projects.

It also addresses: https://gitlab.com/gitlab-org/gitlab-workhorse/issues/4

Next Steps

- create a set of duplicate tags in workhorse to prevent errors when updating from the patch guide


See merge request !3088

Build status `canceled` if any of the jobs canceled

Before this change in case of any of the jobs had been canceled, build status was `failed`.

Closes #14207

See merge request !3778

Use ActionDispatch Remote IP for Akismet checking

Previously all remote IPs appeared at 127.0.0.1, which made Akismet
not very useful. Using the ActionDispatch Remote IP (http://api.rubyonrails.org/classes/ActionDispatch/RemoteIp.html)
should provide more reliable results.

Closes #16629

See merge request !3961

Users can use the feature proposal label inside the issue

Got the idea from https://gitlab.com/gitlab-org/gitlab-ce/issues/12620.

\cc @JobV @sytses 

See merge request !2574

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

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

Send 'admin emails' weekly, not daily

Daily seems to be to spammy, so let's default to weekly instead.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15520

See merge request !3923

[ci skip]

Update using_docker_build.md, clarify the 'privileged' mode requirement

Related to #15428

Fixes gitlab-org/gitlab-ci-multi-runner#1261

See merge request !3909

[ci skip]

Backport GitHub Enterprise import support from EE

These changes were pulled from GitLab EE to support configuring
an alternative API URL than the default https://api.github.com.
In addition, the `verify_ssl` flag allows users to disable SSL cert
checking.

One modification: add a default `args` option if it does not exist
to avoid breaking existing configurations.

See merge request !3892

Previously all remote IPs appeared at 127.0.0.1, which made Akismet
not very useful. Using the ActionDispatch Remote IP (http://api.rubyonrails.org/classes/ActionDispatch/RemoteIp.html)
should provide more reliable results.

Closes #16629

Add JS prefix to user tab classes

## What does this MR do

This MR adds the `js-` prefix to the classes which are used for js purposes only. This MR only affects the said classes inside `users/show.html.haml`.

## Are there points in the code the reviewer needs to double check?

I'm not entirely sure if this project uses the `js-` prefix for
classes that are used for js purposes only. Doing a grep shows some of the classes have the prefix, but I'm still unsure whether this project follows this rule.

## Why was this MR needed?

As I was working thru #13401, I wanted to add a tab on the user profile page to show the contributions outside the GitLab instance. Reading the JS, I came across this. This MR helps new people reading the code that the said classes are for js purposes only. Also, it helps the project work toward to uniform class naming.

I suggest that we document adding the `js-` prefix to classes for js purposes only (if this is the case for this project)

See merge request !3928

Add API doc example with query string for triggering build

Make this explicit to prevent confusion as we saw in gitlab-org/gitlab-ci#413.

See merge request !3947

Sidekiq MemoryKiller sends a `SIGKILL` signal, not `SIGTERM`

As documented in https://gitlab.com/gitlab-org/gitlab-ce/blob/f127edd012bd8b6f76ac67d69aadbd7d4837258f/lib/gitlab/sidekiq_middleware/memory_killer.rb#L10 (this was changed by c291ff9c).

See merge request !3927

Project title dropdown tests

Added a test for when on an issue page to check whether the project
dropdown links will still work

See !3870

See merge request !3921

Updated label links to work correctly for filtering

See !3846#note_5033951

See merge request !3920

Escape key closes the dropdown

Fixes #15432 

![esc](/uploads/067e32bcaf265c3241d84dcbd3f11532/esc.gif)

See merge request !3904

Grack::Auth already checks this variable. These holdouts were not
disabled, leading to confusion when debugging a customer issue.

Changes support from IE 10+ to IE 11+

IE 11 was released 17 October 2013; 2 years ago. Generally what I have experienced is that support for browsers (when newer ones are available) continues for up to 2 years. Based on that info we would drop support for IE 10 and the latest IE we would support would be IE 11. 

I also think this is more realistic since no one is really testing anything on IE 10 at the moment.  We should start testing on all the browser that we currently support. 

Also we can then have real support for flexbox and not need things like `-ms-flexbox` and other IE specific hacks. 

cc @iamphill @annabeldunstone @elvongray @alfredo1 @rspeicher 

See merge request !3913

Add letter_opener_web gem

Sent emails in the development environment will no longer automatically
be opened in the browser. If a sent email needs to be viewed, it can be
found at the `/rails/letter_opener` route.

See merge request !3893

Closes #14090