| Age | Commit message (Collapse) | Author |
|---|
|
When a user checks the `accept` checkbox, we will track that
acceptance as usual. That way they don't need to accept again after
they complete the registration.
When an unauthenticated user visits the `/-/users/terms` page, there
is no button to accept, decline or continue. The 'current-user menu'
is also hidden from the top bar.
|
|
|
|
Resolve "Timeout searching group issues"
Closes #46648
See merge request gitlab-org/gitlab-ce!19429
|
|
38542-application-control-panel-in-settings-page
|
|
Customizable favicon
Closes #15661
See merge request gitlab-org/gitlab-ce!14497
|
|
Backport of 5942-extract-ee-specific-files
See merge request gitlab-org/gitlab-ce!19285
|
|
Pass request to oauth creation during cluster app install
Closes #47459
See merge request gitlab-org/gitlab-ce!19522
|
|
'master'
Resolve "Label list page redesign with draggable labels"
Closes #39549
See merge request gitlab-org/gitlab-ce!18466
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
When filtering issues with a search string in a group, we observed on GitLab.com
that Postgres was using an inefficient query plan, preferring the (global)
trigram indexes on description and title, rather than using a filter on the
restricted set of issues within the group.
Change the callers of the IssuableFinder to use a CTE in this case to fence the
rest of the query from the LIKE filters, so that the optimiser is forced to
perform the filter in the order we prefer.
This will only force the use of a CTE when:
1. The use_cte_for_search params is truthy.
2. We are using Postgres.
3. We have passed the `search` param.
The third item is important - searching issues using the search box does not use
the finder in this way, but contructs a query and appends `full_search` to
that. For some reason, this query does not suffer from the same issue.
Currenly, we only pass this param when filtering issuables (issues or MRs) in a
group context.
|
|
'39549-label-list-page-redesign-with-draggable-labels'
# Conflicts:
# app/views/projects/labels/index.html.haml
|
|
422 status
We have a number of import errors occurring with 422 errors, and
it's hard to determine why they are happening. This change will
surface the errors in the log lines.
Relates to #47365
|
|
|
|
Show a more helpful error for import status
Closes #47365
See merge request gitlab-org/gitlab-ce!19467
|
|
We had `item_project_ids` to help make slow queries on the dashboard faster, but
this isn't necessary any more - the queries are plenty fast, and we forbid
searching the dashboard without filters.
|
|
|
|
GraphQL setup: Basic Project and Merge request endpoint
Closes #34754
See merge request gitlab-org/gitlab-ce!19008
|
|
There's no need to add a redundant message to the errors if the
model is invalid. This cleans up the message as well for the importer.
|
|
Importing a project from GitHub for a project namespace that already exists
would show an unhelpful error, "An error occurred while importing project."
We now add the base message from Projects::CreateService when this fails.
Closes #47365
|
|
'47196-actionview-missingtemplate-missing-template-projects-merge_requests-invalid-projects-merge_requests-application-invalid-pr' into 'master'
Resolve "ActionView::MissingTemplate: Missing template projects/merge_requests/invalid, projects/merge_requests/application/invalid, pr..."
Closes #47196
See merge request gitlab-org/gitlab-ce!19356
|
|
39549-label-list-page-redesign-with-draggable-labels
|
|
Backport of "Extract EE specific files/lines for app/controllers/groups"
See merge request gitlab-org/gitlab-ce!19343
|
|
|
|
|
|
#close_merge_request_without_source_project -> close_merge_request_if_no_source_project
|
|
This allows us to report JSON parse exceptions to clients and ignore
them in sentry.
|
|
|
|
'backstage/gb/use-persisted-stages-to-improve-pipelines-table'
# Conflicts:
# db/schema.rb
|
|
Resolve "Missing Accept button for terms of service"
Closes #46585
See merge request gitlab-org/gitlab-ce!19156
|
|
[CE-backbport] Render a 403 when showing an access denied message
See merge request gitlab-org/gitlab-ce!19415
|
|
Rephrase Merge Request Maintainer Edit
See merge request gitlab-org/gitlab-ce!19061
|
|
|
|
|
|
|
|
|
|
'backstage/gb/use-persisted-stages-to-improve-pipelines-table'
# Conflicts:
# db/schema.rb
|
|
39549-label-list-page-redesign-with-draggable-labels
|
|
Support presigned multipart uploads
See merge request gitlab-org/gitlab-ce!18855
|
|
When we want to show an access denied message to a user, we don't have
to hide the resource's existence.
So in that case we render a 403, this 403 is not handled by nginx on
omnibus installs, making sure the message is visible to the user.
|
|
'backstage/gb/use-persisted-stages-to-improve-pipelines-table'
Conflicts:
app/models/ci/pipeline.rb
|
|
Include all ancestors milestones in json list & autocomplete
Closes #36862
See merge request gitlab-org/gitlab-ce!19317
|
|
We show a blue flash banner if the user already accepted, and show a
button allowing them to continue to the application.
|
|
|
|
|
|
|
|
Since we don't show the archived projects, we shouldnot load them and
pass them to the fronted to be filtered out again.
|
|
|
|
|
|
'master'
Improve validations for Ci::Runner#runner_type
See merge request gitlab-org/gitlab-ce!18901
|
|
because of SSRF
|
