Otherwise we'd only preload the ancestors that would fit the
page. That way, when a search result was on the first page, but the
ancestor didn't fit the page anymore. We would not have the preloaded
ancestor when rendering the hierarchy.

When a project is shared with a group, it should not be included as a
descendant on the group dashboard.

When searching we would limit the scope of ancestors to load because
the filter would be applied to the ancestors. Instead, we need to load
_all_ ancestors for matching projects.

Html code now works in commits atom feed `title` and `summary`.

Given no search term, the `search` and `search_with_secondary_emails` methods will yield an empty result set

Without this, it's very hard to locate it.

Put back non triggered information

Jan Christophersen authored 7 years ago and James Lopez committed 7 years ago

Resolve "Projects API: filter 'with_issues_enabled=true' returns projects with 'issues_enabled=false'"

Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/42157
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/41989