Age | Commit message (Collapse) | Author |
|
See http://asciidoctor.org/docs/user-manual/#include-directive
|
|
Fix sidebar flyout navigation
See merge request gitlab-org/gitlab-ce!29571
|
|
Issue 62684
See merge request gitlab-org/gitlab-ce!29430
|
|
inherit require 2fa for all subgroups and projects
See merge request gitlab-org/gitlab-ce!24965
|
|
Speed up commit loads by disabling BatchLoader replace_methods
See merge request gitlab-org/gitlab-ce!29633
|
|
|
|
We've seen a significant performance penalty when using
`BatchLoader#__replace_with!`. This defines methods on the batch loader
that proxy to the 'real' object using send. The alternative is
`method_missing`, which is slower. However, we've noticed that
`method_missing` can be faster if:
1. The objects being loaded have a large interface.
2. We don't call too many methods on the loaded object.
In production, we've seen the rendering times of the merge request
widget increase as a result of loading commit data. BatchLoader attempts
to call replace_methods on the lazy object, but this has a significant
performance penalty. Disabling this mode
(https://github.com/exAspArk/batch-loader/pull/45) appears to cut load
times by about 50% for MergeRequestsController#show.
Relates to https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6941
|
|
Omit blocked admins from repository check e-mails
Closes #63019
See merge request gitlab-org/gitlab-ce!29507
|
|
Clean up issue-62684
Update issue-62684 changelog
Update down migrate for issue-62684
|
|
|
|
Commit messages are not processed for references to issues when
creating the default branch on push. This was expected
behavior (probably to avoid performance problems when first pushing a
repository with thousands of commits). However, this is not an issue
because we always limit the number of commits to process to 100
regardless of whether we are creating the default branch or not.
|
|
Bring propagated SAST ENV vars into parity with docs
See merge request gitlab-org/gitlab-ce!29564
|
|
Moves sp.js to CE repo
Closes gitlab-ee#12106
See merge request gitlab-org/gitlab-ce!29545
|
|
'61157-reviewer-roulette-shouldn-t-include-the-author-as-a-possibility' into 'master'
Review roulette excludes mr_author
Closes #61157
See merge request gitlab-org/gitlab-ce!28886
|
|
when changing
|
|
|
|
Show flyout nav for active item when collapsed.
|
|
Blocked admins should not receive notifications about failed repository
checks.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63019
|
|
Excludes MR author from gitlab_ui and single_codebase Review roulette
results.
|
|
|
|
long words
|
|
Fix "Resolve conflicts" button not appearing for some users
Closes #47954
See merge request gitlab-org/gitlab-ce!29535
|
|
|
|
|
|
Fix null source_project_id in pool_repositories
Closes gitaly#1653
See merge request gitlab-org/gitlab-ce!29157
|
|
|
|
Fix diverged branch locals
See merge request gitlab-org/gitlab-ce!29508
|
|
|
|
|
|
'master'
Resolve "Remove unnecessary decimal places on chart axes"
Closes #59651
See merge request gitlab-org/gitlab-ce!29468
|
|
Add EE backport for the admin view
See merge request gitlab-org/gitlab-ce!29268
|
|
Moves table pagination component
Closes #62788
See merge request gitlab-org/gitlab-ce!29543
|
|
Expose default_git_depth via project API
Closes #62908
See merge request gitlab-org/gitlab-ce!29353
|
|
|
|
Removes ce to ee differences for snowplow file
|
|
CE backport for gitlab-org/gitlab-ee!12156: Update the merge request widget's "Merge" button to support merge trains
See merge request gitlab-org/gitlab-ce!27594
|
|
Move the table paginaiton component under the
new pagination folder in vue shared components
and updates all the paths
|
|
'62300-target-area-for-dropdown-list-items-is-too-small-on-metrics-dashboard' into 'master'
Resolve "Target area for dropdown list items is too small on Metrics Dashboard"
Closes #62300
See merge request gitlab-org/gitlab-ce!29458
|
|
Enable Get and Update of ci_default_git_depth for
Project API.
Renaming Project#default_git_depth to :ci_default_git_depth
to give more context through the API usage.
Add API documentation
|
|
Document that milestones and labels are still accesible
through direct links when issues are disabled even if
links are missing in sidebar UI.
|
|
|
|
Previously the frontend assumed that the user had to be able to merge to
that project in order to resolve conflicts. However, this is overly
restrictive, as the user only has to be able to push to the source
branch. In fact, appending the text /conflicts to the merge request
would bring up the conflict resolution page.
This confusion happens when a project contains a protected branch that
only allows maintainers to push. Users with Developer access no longer
have permission to merge, but they still can create branches in that
project.
To fix this issue, we now loosen the permission check for the "Resolve
conflicts" button and only check for access to push to the source
branch. This is consistent with what the backend does in
MergeRequests::Conflicts::ListService#can_be_resolved_by?.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/47954
|
|
|
|
|
|
**How?**
It looks like when assignees are clicked, the child of the `<a>`.
We fix our propogation check by looking at `.closest` which traverses
through the element itself and parent.
|
|
Revert "Automatically update MR merge-ref along merge status"
See merge request gitlab-org/gitlab-ce!29492
|
|
Creates pagination component graphql
Closes #62788
See merge request gitlab-org/gitlab-ce!29277
|
|
|
|
Fix pipeline schedule when owner is nil
Closes gitlab-com/gl-infra/production#805 and #63086
See merge request gitlab-org/gitlab-ce!29477
|
|
Due to a bug, some pool_repositories in production have a null
source_project_id column. This migration aims to fix those rows.
|