Age | Commit message (Collapse) | Author |
|
Don't use rugged in Repository#refs_hash
Closes gitaly#880
See merge request gitlab-org/gitlab-ce!16827
|
|
The refs hash is used to determine what branches and tags have a commit
as head in the network graph. The previous implementation depended on
Rugged#references. The problem with this implementation was that it
depended on rugged, but also that it iterated over all references and
thus loading more data than needed if for example the project uses CI/CD
environments, Pipelines, or Merge Requests.
Given only refs are checked the network cares about the GraphHelper#refs
method has no need to reject those, simplifying the method.
Closes gitlab-org/gitaly#880
|
|
into 'master'
Resolve "Add domain field to Auto DevOps application setting"
Closes #38175
See merge request gitlab-org/gitlab-ce!16604
|
|
Override group sidebar links
See merge request gitlab-org/gitlab-ce!16942
|
|
|
|
|
|
Add feature highlight blue dot to GKE "Clusters" sidebar item
Closes #41672
See merge request gitlab-org/gitlab-ce!16379
|
|
From https://gitlab.com/gitlab-org/gitlab-ce/issues/36760
Was reverted in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14373
|
|
|
|
|
|
|
|
|
|
|
|
|
|
38175-add-domain-field-to-auto-devops-application-setting
|
|
Automatically Generate Webpack Entry Points
See merge request gitlab-org/gitlab-ce!16865
|
|
38175-add-domain-field-to-auto-devops-application-setting
|
|
|
|
including/extending it
|
|
|
|
|
|
|
|
|
|
|
|
Backport changes in the application settings helper to CE
See merge request gitlab-org/gitlab-ce!16801
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
38175-add-domain-field-to-auto-devops-application-setting
|
|
Callers expect a URL.
This fixes the avatars in commit lists when a user has no avatar and
Gravatar is disabled.
Closes #38715
|
|
|
|
Fix local RSpec tests due to bug in `webpack_bundle_tag`
Closes #42368
See merge request gitlab-org/gitlab-ce!16724
|
|
breaking local rspec tests
|
|
|
|
Search query is especially slow if a user searches a generic string
which matches many records, in such case search can take tens of
seconds or time out. To speed up the search query, we search only for
first 1000 records, if there is >1000 matching records we just display
"1000+" instead of precise total count supposing that with such amount
the exact count is not so important for the user.
Because for issues even limited search was not fast enough, 2-phase
approach is used for issues: first we use simpler/faster query to get
all public issues, if this exceeds the limit, we just return the limit.
If the amount of matching results is lower than limit, we re-run more
complex search query (which includes also confidential issues).
Re-running the complex query should be fast enough in such case because the
amount of matching issues is lower than limit.
Because exact total_count is now limited, this patch also switches to
to "prev/next" pagination.
Related #40540
|
|
|
|
Resolve "Password authentication enabled for Git over HTTP(S) can not be disabled via UI"
Closes #42206
See merge request gitlab-org/gitlab-ce!16577
|
|
ApplicationSettingsController
|
|
Show why a notification email was sent
Closes #41532 and #1366
See merge request gitlab-org/gitlab-ce!16160
|
|
|
|
Use last_edited_at instead of updated_at for displaying issuable last change
Closes #41247
See merge request gitlab-org/gitlab-ce!16406
|
|
Remove unnecessary query from labels dropdown
Closes #37143
See merge request gitlab-org/gitlab-ce!16520
|
|
|
|
For issuable models we keep two timestamps:
updated_at which is updated whenever any model attribute is changed,
last_edited_at which is changed when only title or description is
changed.
In UI bellow description we display who and when updated the item. But
last_edited_by (used for 'who') is mistakenly combined with updated_at
(when), last_edited_at should be used instead.
Closes #41247
|
|
|
|
Adds `#build_notification_recipients` to `NotificationRecipientService`
that returns the `NotificationRecipient` objects in order to be able to
access the new attribute `reason`.
This new attribute is used in the different notifier methods in order to
add the reason as a header: `X-GitLab-NotificationReason`.
Only the reason with the most priority gets sent.
|