- move issue trackers properties to
a separated table
- keep backwards compatibily and still be able to read
from properties

Add note on expose_path helper usage to API docs

See merge request gitlab-org/gitlab!16797

Remove Ruby elasticsearch repository indexer

See merge request gitlab-org/gitlab!15641

Add review app cluster health troubleshooting guidance

See merge request gitlab-org/gitlab!16520

Fix all instances of no-unused-vars

See merge request gitlab-org/gitlab!16684

Migrate approvals_before_merge column to a rule

See merge request gitlab-org/gitlab!16121

Set default http status of a successful ServiceResponse

See merge request gitlab-org/gitlab!16608

Docs: update Time Tracking

See merge request gitlab-org/gitlab!16627

Update "slash commands" to "quick actions"

Fix analytics dropdown deselect bug

See merge request gitlab-org/gitlab!16778

Disable interruptible pipeline feature flag by default

See merge request gitlab-org/gitlab!16786

Fix naming of constant

See merge request gitlab-org/gitlab!16769

Allow Danger commit_messages rule to work locally

See merge request gitlab-org/gitlab!16593

Avoid Devise "401 Unauthorized" responses

Closes #29155

See merge request gitlab-org/gitlab!16519

Update Dep. Scanning supported languages

See merge request gitlab-org/gitlab!16614

Remove a note saying that Dependency Scanning for Python
is limited to requirements.txt files, since setup.py
is also supported.

Add restricted user/group protected branch test

Closes gitlab-org/quality/testcases#117

See merge request gitlab-org/gitlab!16358

Makes configuring projected branch roles compatible with adding a
user or group when using EE.

Adds some login convenience methods.

Allows projects and groups to add members.

This is part of a larger process of getting rid of all eslint-disable

Productivity Analytics: Add yAxis formatter to column charts

See merge request gitlab-org/gitlab!16744

- This display axis labels as 0.5 instead of 500m

Removes unnecessary externalization of strings

See merge request gitlab-org/gitlab!16628

Fix issue redirects going to /issues/:id/designs

Closes #31357

See merge request gitlab-org/gitlab!16638

Ensure error is raised

Add rake tasksto install golang indexer for installation from source

Set default whitespace diff

Closes #18761

See merge request gitlab-org/gitlab!16570

Docs: Add deploy service requirement

See merge request gitlab-org/gitlab!16686

When a project is redirected to a new project, Rails attempts to
construct the proper URL in `url_for` by finding the first route that
matches the given parameters. In this case, `namespace_id`,
`project_id`, `id` matched the `/designs` route first, so it used that.

This happens because the Rails `resources` block defines all the
standard #index, #show, #update, etc. routes after the block runs.

To ensure that `/issues/:id` is used to display an issue, we need to use
a separate action for `/issues/:id/designs`.

Closes https://gitlab.com/gitlab-org/gitlab/issues/31357

Fix merge request redirects going to /commits page

See merge request gitlab-org/gitlab!16705

Document `only/except: external_pull_requests`

Closes #31660

See merge request gitlab-org/gitlab!16448

Fix spelling mistake in README.md

See merge request gitlab-org/gitlab!16736

When a merge request is redirected to a new project, Rails attempts to
construct the proper URL in `url_for` by finding the first route that
matches the given parameters:

1. `controller` -> `projects/merge_requests`
2. `action` -> `show`
3. `namespace_id`
4. `project_id`
5. `id`

In this example, `/*namespace_id/:project_id/commits/*id` matched
instead of `/*namespace_id/:project_id/merge_requests/:id`.

This happens because the Rails `resources` block defines all the
standard #index, #show, #update, etc. routes after the block runs.

We fixed this issue by explicitly specifying the merge request #show
as the first route.

This is similar to https://gitlab.com/gitlab-org/gitlab/issues/31357,
except the solution is a bit simpler because the backend appears to set
a `tab` query string, which allows the redirected route to end up in the
right place. For example, visiting the old `/merge_requests/:id/commits`
appears to cause a redirection to `/merge_requests/:id/?tab=commits`,
which does the right thing.