Fix incorrect spec filenames which were ingored by CI

See merge request !10875

Added test to prevent ‘Request access’ regression

See merge request !10866

Fix updating merge_when_build_succeeds via merge API endpoint

Closes #22740

See merge request !10873

Database SSL support for backup script.

Closes #1440

See merge request !9715

Fix 9.1 Gitaly source update steps

Closes #31288

See merge request !10877

docs(api): add curl arguments for file upload

See merge request !10848

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

Except where necessary, use `sign_in` over `login_as` in features

See merge request !10320

Make location of gitlab_workhorse_secret configurable

See merge request !10357

Add index on ci_builds.updated_at

Closes #31251

See merge request !10870

When updating a merge request via the `/merge` endpoint we
check the `mergeable` and `mergeable_state` status, these will return
`false` if the application option only_allow_merge_if_pipeline_succeeds is
enabled. We should skip CI checks if the request uses the
merge_when_pipeline_succeeds param

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/22740

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

Add a transaction around `move_issues_to_ghost_user`

See merge request !10465

Fix wrong link to GDK in README file

Closes #30817

See merge request !10701

Mention new mechanism to generate frontend fixtures

See merge request !10706

[#29801] Add "Slack Slash Commands" to API docs

Closes #29801

See merge request !10757

Update plantuml.md Fix wrong order when restarting tomcat service [ci skip]

See merge request !10855

Fix border color on activities page

Closes #31072

See merge request !10864

- While deleting a user, some of the user's associated records are moved to the
  ghost user so they aren't deleted. The user is blocked before these records
  are moved, to prevent the user from creating new records while the migration
  is happening, and so preventing a data race.

- Previously, if the migration failed, the user would _remain_ blocked, which is
  not the expected behavior. On the other hand, we can't just stick the block +
  migration into a transaction, because we want the block to be committed before
  the migration starts (for the data race reason mentioned above).

- One solution (implemented in this commit) is to block the user in a parent
  transaction, migrate the associated records in a nested sub-transaction, and
  then unblock the user in the parent transaction if the sub-transaction fails.

- Reorder slash command api requests, include slack response example
- Case fix and added changelog

submodule_links: handle urls that don't end with .git

See merge request !10799

[ci skip]

Reword backup & restore secrets description

See merge request !10753

Fix Git repository URL field on New Project page

See merge request !10803

Merge branch '31265-update-auto-deploy-documentation-for-postgres-and-private-project-support' into 'master'

Update Auto Deploy documentation

Closes #31265

See merge request !10859

Remove reference to burndown charts since they don't exist for ce.

See merge request !10861

fix placeholder visibility

Closes #30618

See merge request !10804

Use master_password for Sentinel

See merge request !10857

Start versioning cached markdown fields

Closes #30672

See merge request !10597

Refactor add_users method for project and group

See merge request !10850