Show a modal instead of redirecting when the ref is ambiguous

Contributes to: #420352
Changelog: other

Adds a modal that allows the creation of a new machine
learning model in the model registry

Clean up BE for SecurityConfigurationController

Remove FF unify_security_configuration

Changelog: added
EE: true

* add specs for environments_helper
* streamline data shape for environments_folder_bundle

Display work item Epic in legacy issue sidebar

For demo purposes, add 2 pages that show how these objects work to pull
docker images out of a Artifact Registry repository.

Only accessible from saas on projects with the feature flag enabled

Account for owner access role when working with project group links

Changelog: fixed

Changelog: fixed

- Utilize the Compare#generated_files method to set diff files as generated
- Add missing generated column for ContextCommit
- Add collapse_generated_diff_files feature flag

Changelog: added

- Previously, each policy was checking the following things:
  - ai_global_switch ops FF enabled
  - AI license available
  - AI feature available via StageCheck
  - Is the user actually a member of the parent resource? (only members
  can use AI features)
- Now, any permissions checks related to AI features can call
  `Llm::FeatureAuthorizer` and be confident that they are making all of
  the correct checks.
- Follow-up to !137362

For the frontend, add a number of paths that are required on the
frontend. These are edit, enable and disable.

Also, rails seems to return nothing instead of an empty list when there
are no deploy keys. The easiest way to fix this is to wrap the return
within a map.

Let's also add frontend fixtures for the new controller endpoints.

Changelog: removed
EE: true

Backend response will depend on whether the search param is given so we
only need to feature flag the frontend

Allows backend filtering for the members autocomplete so that we don't
have to render a very large JSON payload when in large projects or
groups

Changelog: fixed

Pam Artiaga authored 1 year ago and Thong Kuah committed 1 year ago

The group and project objects are called in a `prepend_before_action`
so that they are fetched before the authorization checks
(e.g.: authorize_admin_cluster, authorize_update_cluster).

However, this results in a bug because fetching the group or project
requires the session to be loaded already, and `prepend_before_action`
calls happen before the session is loaded.

To resolve the problem, we will instead load the group or project
object in the very first `before_action` in the ClustersController
call stack.

Changelog: fixed

Marc Saleiko authored 1 year ago and Felipe Cardozo committed 1 year ago

You can set to automatically reopen an issue when it
receives a new note from an external participant by email
on the project's Service Desk settings page.

Changelog: added

Jacques Erasmus authored 1 year ago and Vasilii Iakliushin committed 1 year ago

Changes the method to the correct encoding

Changelog: fixed

Changelog: added

Introduce the jump to job log failures
button.

Changelog: added

Andrew Fontaine authored 1 year ago and Michał Zając committed 1 year ago

This will give the frontend the ability to fetch a specific set of
deploy keys at at time, reducing page load times and DB query time.

Brett Walker authored 1 year ago and Miguel Rincon committed 1 year ago

for a merged MR

Changelog: added

Eduardo Bonet authored 1 year ago and Vitali Tatarintev committed 1 year ago

- Model registry expects json to be camelCased and not snake_cased.
- separates on CandidateDetailPresenter present from present_as_json so that the data is reusable in
other Components.
- Adds prop to hide part of the rendered information about a candidate

Marc Saleiko authored 1 year ago and Kerri Miller committed 1 year ago

Changelog: other

Tiger Watson authored 1 year ago and GitLab Release Tools Bot committed 1 year ago

Merge branch 'security-add-tags-releases-access-check' into 'master'

See merge request gitlab-org/security/gitlab!3668

Changelog: security

Andrei Zubov authored 1 year ago and Andrew Fontaine committed 1 year ago

* add vue component for new folders page
* add feature toggle environmens_folder_new_look
* add related specs

Phil Hughes authored 1 year ago and Kushal Pandya committed 1 year ago

This adds the checks component into the widget app so that it renders
to users.
Also added realtime to the merge checks component by
using an existing subscription.

Baodong authored 1 year ago and Andy Schoenen committed 1 year ago

Changelog: removed

This reverts merge request !135170

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/136993
Changelog: other

Joseph Wambua authored 1 year ago and Michael Kozono committed 1 year ago

Guest role is required when linking issues as related, blocked or
blocking.

Changelog: changed
EE: true

Hordur Freyr Yngvason authored 1 year ago and Alper Akgun committed 1 year ago

Split out of
!135276, as it was
getting too large and we should start getting parts of this merged. This
only adds a feature flagged project setting (it does not implement the
updated mergeability check).

When "Pipelines must succeed" is selected, it is currently not possible
to merge without a pipeline. This includes cases where the configuration
is technically valid, but the pipeline is intentionally not created, such
as:

- pipeline was omitted because no jobs matched `rules` and `only/except`
- pipeline was omitted via `workflow:rules`
- there was no `.gitlab-ci.yml`

Changing this behavior is not backwards-compatible, because there is no
way of knowing if an external CI system is running for a given change.
So we add a project setting instead.

See #334281

Changelog: changed

Changelog: added

The `ck` param is used by the client (e.g. browser) to cache the
request on client side.

We are previously using the `MergeRequestDiff#id` which can change
often since we regenerate the HEAD diff when target branch changes
as well.

To ensure that the client cache doesn't invalidate often, we utilize
the `MergeRequestDiff#patch_id_sha` so `ck` won't change if the diff
didn't really change when the diff was regenerated.

This is behind `diffs_batch_cache_with_max_age` feature flag.

Manav Agarwal authored 1 year ago and Phil Hughes committed 1 year ago

Using a constant in the first batch of diff files
for the file amount instead of a hard coded value

Changelog: changed

Changelog: added