This will be disallowed again once the existing benchmarks pass (which
relies on #2341).

This class method can be used in "describe" blocks to specify the
subject of a benchmark. This lets you write:

    benchmark_subject { Foo }

instead of:

    benchmark_subject { -> { Foo } }

This benchmark suite uses benchmark-ips
(https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can
be turned into benchmark specs by setting "benchmark" to "true" in the
top-level describe block like so:

    describe SomeClass, benchmark: true do

    end

Writing benchmarks can be done using custom RSpec matchers, for example:

    describe MaruTheCat, benchmark: true do
      describe '#jump_in_box' do
        it 'should run 1000 iterations per second' do
          maru = described_class.new

          expect { maru.jump_in_box }.to iterate_per_second(1000)
        end
      end
    end

By default the "iterate_per_second" expectation requires a standard
deviation under 30% (this is just an arbitrary default for now). You can
change this by chaining "with_maximum_stddev" on the expectation:

    expect { maru.jump_in_box }.to iterate_per_second(1000)
      .with_maximum_stddev(10)

This will change the expectation to require a maximum deviation of 10%.

Alternatively you can use the it block style to write specs:

    describe MaruTheCat, benchmark: true do
      describe '#jump_in_box' do
        subject { -> { described_class.new } }

        it { is_expected.to iterate_per_second(1000) }
      end
    end

Because "iterate_per_second" operates on a block, opposed to a static
value, the "subject" method must return a Proc. This looks a bit goofy
but I have been unable to find a nice way around this.

If this directory were to be empty this would result in warnings being
printed to STDERR, cluttering spec output. Doing this in Ruby fixes this
problem (and also removes the need for shell alltogether).

Back and forth permission on builds/

@jacobvosmaer I missed that :(


See merge request !1500

Ensure GitLab CI project exists when CI service is activated manually

When I check activeated checkbox in project services for GitLab CI it
cause half-working state when gitlab_ci_project is missing. This patch
fixes it until we have proper behaviour implemented later

This fix also bring us to the point when fork of project is a bit broken and have unnecessary code so I made cleanup. 
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

cc @ayufan 

See merge request !1491

This allows me to use this Gem for benchmarking without having to
add/remove it every time.

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>

Add last push widget to starred projects dashboard

This adds the last push widget to the starred projects dashboard. If a user set the starred projects dashboard as their preferred dashboard they would not see last push widget. The look is seamless between starred and 'your projects' dashboards.

### Screenshot:

![Screen_Shot_2015-10-01_at_3.15.52_PM](https://gitlab.com/gitlab-org/gitlab-ce/uploads/2f5dcf49c3d0186bdd05bb6788b143f1/Screen_Shot_2015-10-01_at_3.15.52_PM.png)


See merge request !1304

Ensure updated notes are syntax highlighted

See merge request !1444

Fix link with emoji

[ci skip]

Change email footer text

Old:

> You're receiving this notification because you are a member of the GitLab.org / GitLab Community Edition project team.

New:

> You're receiving this notification because you've contributed to the GitLab.org / GitLab Community Edition project.


See merge request !1409

Update gitlab_git to 7.2.17

Fixes #2316.

See merge request !1464

Fix path to /etc/default/gitlab in 8.0 update guide



See merge request !1437

Link to rake tasks

I believe there should be a link to rake tasks from backup restore, to give the user more options. That is why I added the link in the documentation. 

Because of tweet https://twitter.com/gordonjb/status/641252693701476352

See merge request !1928

New doc about how to create an issue in GitLab Basics



See merge request !1925

When I check activeated checkbox in project services for GitLab CI it
cause half-working state when gitlab_ci_project is missing. This patch
fixes it until we have proper behaviour implemented later
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Removes reference to Enterprise Edition ssh key sync feature.

fixes #2042

See merge request !1017

notify: fix typo in merged_merge_request_email template

All (two) other templates with this line use 'url' rather than 'Url'.

See merge request !1151

Make Visit project on GitLab button goes to The internal Gitlab project

Since we are merging CI into CE, projects should go to the internal Projects
page, we can also use Turbolinks to do so.

In order to give the user an idea of integration, I renamed the button: "Go to
Project"

![image](https://gitlab.com/jeroenvanbaarsen/gitlab-ce/uploads/e4134716680e37b3211c3b5fd6118d1e/image.png)


See merge request !1344

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

Add support of multibyte characters in LDAP UID



See merge request !1472

Improve UI for list of changed files

* fix paddings
* re-use system colors

## Before

![Screenshot_2015-10-01_12.46.24](https://gitlab.com/gitlab-org/gitlab-ce/uploads/3a02fe2beb47637c664eb914dbec352c/Screenshot_2015-10-01_12.46.24.png)


## After

![Screenshot_2015-10-01_12.54.39](https://gitlab.com/gitlab-org/gitlab-ce/uploads/39b1bf78983b862b559fcc89c52d5690/Screenshot_2015-10-01_12.54.39.png)


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

See merge request !1484

Fix  random 500 error on compare page
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Bug appeared after recent mr !1471  

See merge request !1486

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

Disable the "Report abuse" button if a user has already been reported

Hello,

I've implemented the feature request #2330. Here is what it looks like:

![report-abuse-button-disabled](https://gitlab.com/rymai/gitlab-ce/uploads/420d51906eac1c40c50701a0a340474f/report-abuse-button-disabled.png)

I hope that's an acceptable solution.

cc @DouweM

See merge request !1456

CI: Fix clone url and fix project token removal

- Fixes broken CI clone url on dev.gitlab.org
- Fixes regression in CI token removal

/cc @vsizov @dzaporozhets 



See merge request !1481

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