Nicolò Mezzopera authored 4 years ago and Andrew Fontaine committed 4 years ago

- source
- tests

[ci skip]

Prevent overlapping iteration dates within same group and within same
iteration cadence set.

Drew Blessing authored 4 years ago and Drew Blessing committed 4 years ago

Migrate the column to namespace_settings in preparation for
cascading namespace settings support for this setting.

Daniel Schömer authored 4 years ago and David O'Regan committed 4 years ago

Project Settings General Headers (h4 elements) expand/collapse on
mouse-click / tap, like using the Expand/Collapse button. Other h4
headers in other Project Settings pages do not expande/collapse on
mouse-click / tap, but only using the Expand/Collapse button. This may
seem inconsistent to the user.

The h4 headers of Project Settings General get the expand/collapse
behavior through classes settings-title, js-settings-toggle and
js-settings-toggle-trigger-only.

This MR adds classes settings-title, js-settings-toggle and
js-settings-toggle-trigger-only to the h4 headers in Project Settings
CI/CD for GitLab FOSS. This enables the expand/collapse behavior on
mouse-click / tap for the h4 headers.

This adds the duration and finished_at fields
to the aforementioned graphql type

When generating a changelog and leaving out the `from` parameter, we no
longer require that the names of tags start with a "v". Instead, tags
can now be in the format `X.Y.Z` or `vX.Y.Z`.

This fixes https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/1572

- fix Group class inside the migration
- add specs checking the correct class is being called
- reschedule the migration

The Webex Teams and Unify Circuit integrations didn't work correctly for
pipeline notifications, because they were using the method
`ChatMessage::PipelineMessage#pretext` which is overriden to always
return an empty string.

We can fix this by calling `#summary` instead, which is also what
`ChatMessage::BaseMessage#pretext` does by default. No other message
types override `#pretext` or `#summary`, so this change should be
backwards-compatible.

Brandon Labuschagne authored 4 years ago and Martin Wortschack committed 4 years ago

This is being done for the blob dropdown
zone functionality within the project
breadcrumbs

This pulls in the changes in
https://gitlab.com/gitlab-org/gitlab-fog-azure-rm/-/merge_requests/21 to
force Azure to encode generated URLs.

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

Eulyeon Ko authored 4 years ago and Jacques Erasmus committed 4 years ago

- Replace Boostrap dropdown with GlDropdown for comment submit button.

- Remove note_dropdown qa selector

- Update the shared example Thread Comments
The shared examples under "Thread Comments" have split into two:
"Thread Comments for commit and snippet"
and "Thread Comments for issue, epic and merge request"

Why?
After we've replaced Bootstrap dropdown button
with GitLab UI counterpart in comment_form.vue,
issue, epic and merge request uses GitLab UI GlDropdown
that has slightly different selectors.

Previously quarantined examples have been restored in this commit:
https://gitlab.com/gitlab-org/gitlab/-/issues/196825

Jan Provaznik authored 4 years ago and Charlie Ablett committed 4 years ago

If number of epic ids we pass to BulkEpicAggregateLoader reaches a limit
(~200), then postgres uses a different plan for the query which is much
slower.

To avoid this situation, we get this metadata in two phases:
1. get epic ids for epics and its descendants (we use pluck because
this query is recursive and find_each wouldn't help here)
2. we iterate in batches and get metadata for each of batch

- Add changelog
- Add changes to services + graphql
- Update specs

- move wiki error alert to vue
- add tests

This reverts https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53326
since the endpoint created from the pre-signed URL is incorrect. For S3
virtual hostnames (e.g. `https://bucket.us-west-1.amazonaws.com`, the
bucket name should be ignored, so the endpoint should be
`https://us-west-1.amazonaws.com` in this case. This causes the wrong
endpoint to be used (`https://bucket.bucket.us-west-1.amazonaws.com`).

A workaround for AWS S3 users is to pass `endpoint: s3.amazonaws.com` as
a config.

Coung Ngo authored 4 years ago and David O'Regan committed 4 years ago

Convert the dropdown from GlDeprecatedDropdown to GlDropdown

This commits gets rid of our existing coverage finder and
the feature flag associated with our new coverage finder.
All codepaths will now use the new finder.

Removes backup_labels table used
previously used by background migrations.

By clearing the search, it makes it easier for users to pick existing
environments, as they are already listed, but filtered out by the
current value.

Nathan Friend authored 4 years ago and David O'Regan committed 4 years ago

This commit updates the ref selector dropdown (used on the "New Release"
page) so that it doesn't show a double scrollbar.

Andrew Fontaine authored 4 years ago and David O'Regan committed 4 years ago

The primary action is now to close the modal and do nothing, while the
secondary action is to rotate the token.

The cancel action is no longer used, as it has become the primary action
instead.

Coung Ngo authored 4 years ago and Natalia Tepluhina committed 4 years ago

When searching for a user, e.g. `@win`, users whose
name OR username starts with `win` are shown as
the top result in the autocomplete menu.

This commit also increases the results list from 5 to 10
for members autocomplete.

The improvements are discussed in
https://gitlab.com/gitlab-org/gitlab/-/issues/118597