By visiting `projects/:id` you will be redirected to project page with
path in it.

projects/123 => foo/bar
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

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

We introduced the feature flag `error_tracking` to test the Sentry MVC
safely.

After the successful test, we remove it again.

The importer would display a 500 error page if you attempted to import
using a non-existent DNS entry. This commit rescues known network issues
and consolidates them into
BitbucketServer::Connection::ConnectionError`.  The previous error
handling in the paginator doesn't work because it returns a lazy
collection.

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

Instead of querying relations into ids we just pass them to the model
scope because the scope supports it now.

Also changes other calls to `Milestone.for_projects_and_groups`

Also remove test for the feature flag

We introduced releases_page feature flag.
Given this feature is deemed stable, we should remove
this flag before 19th.

By default in Rails 5, content passed to `render` will be
escaped. This doesn't work for the HTML profile output, which
should be considered safe HTML already.

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

Replacing inline JS with ES 2015 functions included in pages/sessions/new. Also applying suggested server-side syntax improvements to OmniAuthCallbacksController.

If window.location contains a URL fragment, append the fragment to all sign-in forms, the sign-up form, and all button based providers.

The original intention of `get_build` was as a workaround not to violate
`CodeReuse/ActiveRecord`. `find_by_id` does the exact same thing but
does not violate the rubocop rule.

Re-use operations controller which already handles tracing settings.

Inside of `Projects::ArtifactsController` and
`Projects::BuildArtifactsController` we fetching the build by id using
active record directly which violates `CodeReuse/ActiveRecord` rubocop
rule. Create `get_build` inside of `project` model which does the same
thing.

`project.latest_successful_builds_for(ref)` is being used to find a
single job all the time. This results into us having to call `find_by`
inside of the controller which violates our CodeReuse/ActiveRecord
rubocop rule.

Refactor `project.latest_successful_builds_for(ref)` to
`project.latest_successful_build_for(job_name, ref)` which will execute
the `find_by` inside of the model.

Also create `project.latest_successful_build_for!(job_name, ref)` which
raises an exception instead of returning nil.

This adds `project:, file:, ref:` specification support.

Load whole file in memory to simplify code

Also refactored cleanup view to use the same localized string

Also changes old calls to the service

Process CSV uploads async using a worker then email results

Added button and modal to accept CSV file for uploading

This commit prepares the structure for the upcoming feature error
tracking.

Add spec for all release API - GET, POST, PUT, DELETE.
Also, fixes some minior bugs.

CreateReleaseService and UpdateReleaseService now takes all the release
attributes as constructor parameters. This will simplify attribute
expansion

This commit introduces Releases API under /api/v4/projects/:id/releases

* We are introducing release policies at project level.
* We are deprecating releases changes from tags, both api and web
interface.
* Tags::CreateService no longer create a release

This feature is controlled by :releases_page feature flag

This commit, introduced in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23812,
fixes a problem creating a displaying image diff notes when the image
is stored in LFS. The main problem was that `Gitlab::Diff::File` was
returning an invalid valid in `text?` for this kind of files.

It also fixes a rendering problem with other LFS files, like text
ones. They LFS pointer shouldn't be shown when LFS is enabled
for the project, but they were.

This commit handles note diffs caching, which considerably improves
the performance on merge requests with lots of comments.
Important to note that the caching approach taken here is different
from `Gitlab::Diff::HighlightCache`. We do not reset the whole cache
when a new push is sent or anything else. That's because discussions
diffs are persisted and do not change.

One of the steps to deprecate dashboard milestones.
Links do dashboard milestone are replaced with links for each
project milestone