Safari 9.0 does not yet honor the HTML5 `origin-when-cross-origin` mode,
and it's possible load balancers/proxies strip the HTTP_REFERER from
the request header. In these cases, default to some default path.

Closes #3122

Closes https://github.com/gitlabhq/gitlabhq/issues/9731

By default, all the current user's repositories are accessible via the
/users endpoint. There's no need to traverse all the organization
repositories as well.

See:

* http://www.rubydoc.info/github/pengwynn/octokit/Octokit/Client/Repositories#repositories-instance_method
* https://developer.github.com/v3/repos/#list-your-repositories

Closes #2523

This cuts down the time it takes to sort issues of a milestone by about
10x. In the previous setup the code would run a SQL query for every
issue that had to be sorted. The new setup instead runs a single SQL
query to update all the given issues at once.

The attached benchmark used to run at around 60 iterations per second,
using the new setup this hovers around 600 iterations per second. Timing
wise a request to update a milestone with 40-something issues would take
about 760 ms, in the new setup this only takes about 130 ms.

Fixes #3066

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

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

Password can now be specified at the same time as the new URL, and the service
template admin pages now work.

This ensures we don't end up running N+1 queries for the objects in the
affected collections.

This reverts commit b4639754.

Slightly refactor runner status detection: moving it to Runner class
Signed-off-by: NKamil Trzcinski <ayufan@ayufan.eu>

It now allows to specify a password at the same time as the new URL, and works
on the service template admin pages.

This allows us to give a nice 404 for e.g. archive.zip.

Changed the authentication method for removing fork through API
Reflected changes to new auth method in API specs

This was previously possible through the API but can now be done
through the project#edit settings screen if the current user is
the owner of the project.
Update changelog

Closes https://github.com/gitlabhq/gitlabhq/issues/8763

Notifications button was unavailable if user wasn't member of the
project, even if protected project is available via group privileges.

Showing disabled button with explanation tool-tip is less confusing.

This closes #2846.

This change relies on changes in gitlab_git and gitlab-git-http-server.