delta/gitlab/gitlab-ce.git/app/helpers, branch docs-pages-force-https

Merge branch '63177-follow-up-from-use-scoped-routes-for-labels-and-milestones' into 'master'

2019-06-25T15:51:48+00:00

Resolve "Follow-up from "Use scoped routes for labels and milestones""

Closes #63177

See merge request gitlab-org/gitlab-ce!29983

Rename to time_tracking_limit_to_hours

2019-06-25T01:31:23+00:00

Changes migration and all other places the attribute is used

Limit time tracking values to hours

2019-06-25T01:31:23+00:00

Adds an instance setting to limit display of time tracking
values to hours only

Eliminate N+1 queries in Dashboard::TodosController

2019-06-24T16:57:38+00:00

This appears to bring down the number of SQL queries on GitLab.com for
my Todos page from 672 to 100.

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

Remove baseEndpoint from search dropdwon

2019-06-24T12:10:15+00:00

Signed-off-by: Dmitriy Zaporozhets

Show create merge request button on confidential issues

2019-06-24T09:50:08+00:00

https://gitlab.com/gitlab-org/gitlab-ce/issues/58583

Memoize non-existent custom appearances

2019-06-23T21:38:44+00:00

This saves about 5 SQL calls per page if no custom appearance is
specified.

Omit issues links in merge request entity API response

2019-06-20T22:59:41+00:00

The merge request widget has a section that includes which issues may be
closed or mentioned based on the merge request description. The problem
is that rendering and redacting Markdown can be expensive, especially
since the browser polls for the data every 10 seconds.

Since these links don't change much and are just nice to have, we only
load them on first page load. The frontend will use the existing data if
the data doesn't appear on subsequent requests.

This saves about 30% of the rendering time of this endpoint, which adds
up to significant savings considering that
`MergeRequestsController#show.json` is called over a million times a day
on GitLab.com.

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

Render GFM html in GraphQL

2019-06-20T08:02:33+00:00

This adds a `markdown_field` to our types.

Using this helper will render a model's markdown field using the
existing `MarkupHelper` with the context of the GraphQL query
available to the helper.

Having the context available to the helper is needed for redacting
links to resources that the current user is not allowed to see.

Because rendering the HTML can cause queries, the complexity of a
these fields is raised by 5 above the default.

The markdown field helper can be used as follows:

      ```
      markdown_field :note_html, null: false
      ```

This would generate a field that will render the markdown field `note`
of the model. This could be overridden by adding the `method:`
argument. Passing a symbol for the method name:

      ```
      markdown_field :body_html, null: false, method: :note
      ```

It will have this description by default:

> The GitLab Flavored Markdown rendering of `note`

This could be overridden by passing a `description:` argument.

The type of a `markdown_field` is always `GraphQL::STRING_TYPE`.

Make KubernetesService readonly

2019-06-18T00:01:56+00:00

We are deprecating this service in favor of instance wide clusters.
Therefore we removed some code that is not anymore needed for a
readonly cluster and also we added some flags to allow for this
deprecation. These flags are to be removed in the next release when
we finally completelly remove KubernetesService.