| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| | |
Migrate Repository#can_be_merged? to Gitaly
Closes gitaly#893
See merge request gitlab-org/gitlab-ce!16316
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Resolve "!15665 consistently 502s because it fetches every commit"
Closes #41807
See merge request gitlab-org/gitlab-ce!16320
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If we search for notes before the MR was merged, we have to load every commit
that was ever part of the MR, or mentioned in a push. In extreme cases, this can
be tens of thousands of commits to load, but we know they can't revert the merge
commit, because they are from before the MR was merged.
In the (rare) case that we don't have a `merged_at` value for the MR, we can
still search all notes.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix Route validation when conflicting permanent redirects exist
Closes gitlab-com/support-forum#2883 and #41786
See merge request gitlab-org/gitlab-ce!16397
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This reverts commit 3576d59ae95a61dd20e997a619dbc6c8e8a70276.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Migrate rebase_in_progress? to Gitaly
Closes gitaly#866
See merge request gitlab-org/gitlab-ce!16286
|
| | | |
| | |
| | |
| | | |
Closes gitaly#866
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove soft removals related code
Closes #37447
See merge request gitlab-org/gitlab-ce!15789
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This removes all usage of soft removals except for the "pending delete"
system implemented for projects. This in turn simplifies all the query
plans of the models that used soft removals. Since we don't really use
soft removals for anything useful there's no point in keeping it around.
This _does_ mean that hard removals of issues (which only admins can do
if I'm not mistaken) can influence the "iid" values, but that code is
broken to begin with. More on this (and how to fix it) can be found in
https://gitlab.com/gitlab-org/gitlab-ce/issues/31114.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Gitlab::Git::Repository#write_ref client-prep take 2
Closes gitaly#793
See merge request gitlab-org/gitlab-ce!16287
|
| | | |/
| |/| |
|
| | | |
| | |
| | |
| | | |
Closes #41739
|
| | | |
| | |
| | |
| | | |
This reverts commit 8040edcce8b4e736b4f4857e6709f94aeb5e274c.
|
| | | |
| | |
| | |
| | | |
This reverts commit a2cb92495c3149b69eb734596e80fbdd54b0b2dc.
|
| | | | |
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Resolve "Fix wrong output protocol pattern when adding custom domain to Pages"
Closes #28260
See merge request gitlab-org/gitlab-ce!16279
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Remove the Commit#tree method
See merge request gitlab-org/gitlab-ce!16236
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Protected branch is now created for default branch on import
Closes #3968
See merge request gitlab-org/gitlab-ce!16198
|
| | |/ |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "Clearing the cache"
Closes #41249
See merge request gitlab-org/gitlab-ce!16067
|
| | |\ \ |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | |_|/ /
|/| | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Backport 'Rebase' feature from EE to CE
Closes #40301
See merge request gitlab-org/gitlab-ce!16071
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a project uses fast-forward merging strategy user has
to rebase MRs to target branch before it can be merged.
Now user can do rebase in UI by clicking 'Rebase' button
instead of doing rebase locally.
This feature was already present in EE, this is only backport
of the feature to CE. Couple of changes:
* removed rebase license check
* renamed migration (changed timestamp)
Closes #40301
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Remove the Project#repo method
See merge request gitlab-org/gitlab-ce!16238
|
| | | |_|/
| |/| | |
|
| | |_|/
|/| | |
|
| |\ \ \
| | | |
| | | |
| | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change is required because otherwise if a user is created with a
value for `projects_limit` that matches the DB default, it gets
overwritten by `current_application_settings.default_projects_limit`. By
removing the default we once again can allow a user to be created with a
limit of 10 projects without the risk that it'll change to 10000
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Eager load event target authors whenever possible
Closes #41618
See merge request gitlab-org/gitlab-ce!16199
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This ensures that the "author" association of an event's "target"
association is eager loaded whenever the "target" association defines an
"author" association. This in turn solves the N+1 query problem we first
tried to solve in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/15788 but caused
problems when displaying milestones as those don't define an "author"
association.
The approach in this commit does mean that the authors are _always_
eager loaded since this takes place in the "belongs_to" block. This
however shouldn't pose too much of a problem, and as far as I can tell
there's no real way around this unfortunately.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Improve closed/merged events queries performance on Projects::MergeRequestsController#show.json
See merge request gitlab-org/gitlab-ce!15642
|
| | |/ / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
