Move status scss into a
page bundle.

Replace done callbacks with async/await, update
to use finders instead of classes and add a
createComponent method

Updates references to use the paperclip svg
instead of fa-paperclip

This commit updates our GraphQL endpiont to allow releases to be
sorted by released_at or created_at.

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

- Remove welcome list
- Create To Do and Doing lists using labels

Track unique MAU for comments added, removed, or edited on Issues

Replace dropdown with input field for EKS Regions
Update authorize_role_service to authenticate with customer region

This change is being done for mr_widget_auto_merge_enabled.vue

If we use a query that doesn't return all the columns, we can get this
error, as we are having using Service.each_batch.

    Failure/Error: self.properties = {} if properties.nil?

    ActiveModel::MissingAttributeError:
      missing attribute: properties
    # ./app/models/service.rb:281:in `initialize_properties'
    # ./app/models/concerns/each_batch.rb:61:in `each_batch'

We have to use has_attribute? to avoid the
ActiveRecord::MissingAttributeError error.

Add general component for instance statistics
count charts to be reused, so the user can both
see issues and merge request data as well as
pipeline statistics. This will also be useful for
other charts on the same page.

Refs:
https://gitlab.com/gitlab-org/gitlab/-/issues/267538
https://gitlab.com/gitlab-org/gitlab/-/issues/246491
https://gitlab.com/gitlab-org/gitlab/-/issues/268224
https://gitlab.com/gitlab-org/gitlab/-/issues/267997
https://gitlab.com/gitlab-org/gitlab/-/issues/233854

Updates `issuable_list` app with following enhancements;

- Custom reference and status support via slots.
- Assignees support.
- Labels permalink support.
- Ability to update page URL using provided params.
- Tab counts are now optional.
- Handle external URLs for Issuable items.

and raise error if sha256 is absent for artifacts archive

Removes the resolve button from each note component
Instead only the first note has this button,
when this button is clicked it resolves the whole thread.

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

Originally, we only call here to propagate service templates if they are
active. Now, we are propagating instance-level integrations and
group-level integrations (active or not).

has_external_issue_tracker and has_external_wiki assume that the
integration is active. So, we only need to update the project callbacks
if the integration is active.

- This replaces the fa-refresh
icon with the retry SVG

This API is available on two levels: Project and Group.
A new field `container_repositories` is available on the Project object
and the Group project

After introducing the propagation of integrations using batching and
queues https://gitlab.com/gitlab-org/gitlab/-/merge_requests/42128, we
are not updating the project callbacks: has_external_issue_tracker and
has_external_wiki.

The reason for that is that the batch was uncached but after the merge
request batch is scoped to the query.

In this case, the order is important because we do two things:
- Create the integration for those projects without integration.
- Update has_external_issue_tracker and has_external_wiki in those
  projects.

If we first create the integrations when we then try to update the
callbacks, there is nothing to update since the batch scope is empty at
this time. We have to update first and then create the integrations.

This fixes the target branch filter in merge requests to allow
the user to filter by not equal.

Enable GitHub Flavored Markdown support for issues to the
search autocomplete field. If the user is in the project
dashboard and enters GFM for an issue id, a link to that
issue will show up.

* Removes conditional feature flag code from specs
* Updates the docs to remove mention of feature flag
* Removes code from CommitStatus model
* Removes yml file with feature flag info

The JSON format handling for snippets#show endpoint does
not appear to be in use since moving to Vue, this commit
removes it to clean up the controllers

Tom Quirk 创作于 4 years ago ，Vitaly Slobodin 提交于 4 years ago

This scopes complexity to the component for better
maintainability

* Update attribute we check to reflect new component attributes

The recursive query for personal namespaces is not performing efficient,
there we'll not use the recursive project lookup for personal
namespaces.

If a user searches for a commit in a project and only finds
one result, redirect the user to that result. This already
exists for basic search and now is enabled for advanced
search. Added a notice explaining the redirect with a
link back to search results.

- Adds unit test

Replace openid_connect_signing_key with the new ci_jwt_signing_key when
generating CI_JOB_JWT.

The new key is stored encrypted in `application_settings` table.

This also implements /-/jwks endpoint instead of delegating to
Doorkeper. Response will still include openid_connect_signing_key for
seamless rollout.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/214607.

* Used on snippets note submit button, for example.
* Also adds support for 'add' to tooltips API.

Part of a larger initiative to convert group members view from HAML
to Vue

when using board finders

Simplifies the data flow of the modal that
contains a form to edit the Merge Request
description and title in the Static Site Editor