Closes #23460

Explored Policy framework to create something I can use as a starting point.

Closes #28857

Before we were using a "plumbing" Gitlab::Git method that does not go
through Gitaly migration checking.

Douwe Maan authored 6 years ago and Mark Fletcher committed 6 years ago

Server Side Request Forgery in Services and Web Hooks

See merge request gitlab/gitlabhq!2337

Partial fix to #44378

and fixes the project description not being imported

Prevents `.gitattributes` blob lookup being repeated for every file checked at a given ref

Attempted commits were failing due to the pre-recieve LfsIntegrity
check. This is skipped during tests making this failure silent.

Previously, we kept them all in the cache. We don't need the highlight results
for older diffs - if someone does view that (which is rare), we can do the
highlighting on the fly.

Updates Files::MultiService for the commits API which is in turn used by the
multi-file upload web UI

Ensures that files which should be in LFS are transformed into LFS pointers
Uses Lfs::Transformer which then links LfsObjectProjects on success

If no parameters were specified for project features but Wikis were disabled,
we would get "NoMethodError: undefined method `[]' for nil:NilClass".

Closes #44019

Using the relation `Project#source_of_merge_requests` in
`Ci::CreatePipelineService`

That way we take advantage of all the `ActiveRecord::Relation` magic

When a project is not private, and the source branch not protected the
user can now select the option to allow maintainers to push to this
branch

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

* adds basic discussions API for issues and snippets
* reorganizes notes specs (so same tests can be used for all noteable types - issues, MRs, snippets)

Deleting a user would fail in the system hooks if the user had
`nil` column in `datetime` or `updated_at` fields.

Closes #43871