GitLab FOSS merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests2017-06-15T11:48:21Zhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/12099Add index to ci_builds for created_at and project2017-06-15T11:48:21ZZeger-Jan van de Wegzegerjan@gitlab.comAdd index to ci_builds for created_at and project## Does this MR meet the acceptance criteria?
- [X] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
## What are the ...## Does this MR meet the acceptance criteria?
- [X] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
## What are the relevant issue numbers?
Hope its a fix for gitlab-org/gitlab-ce#32407, but not closing it until its clear.Zeger-Jan van de Wegzegerjan@gitlab.comZeger-Jan van de Wegzegerjan@gitlab.comhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6292Use foreign keys with cascade delete to optimize project removal2017-06-09T15:53:59Zusername-removed-367626Use foreign keys with cascade delete to optimize project removal## What does this MR do?
Use foreign keys with cascade delete to optimize project removal
## Are there points in the code the reviewer needs to double check?
We should test this in staging and see if the migration runs through withou...## What does this MR do?
Use foreign keys with cascade delete to optimize project removal
## Are there points in the code the reviewer needs to double check?
We should test this in staging and see if the migration runs through without problem, and how long it takes
## Why was this MR needed?
Deleting a project results in an absurd amount of queries for big projects
## Does this MR meet the acceptance criteria?
- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [x] Added for this feature/bug
- [ ] All builds are passing
- [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #11639.0username-removed-367626username-removed-367626https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10573Fix performance regression when displaying builds and pipelines2017-05-15T07:59:58ZKamil TrzcińśkiFix performance regression when displaying builds and pipelines## What does this MR do?
Fixes performance regression introduced after merging https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10462, after noticing performance degredation on `dev.gitlab.org`: https://performance.gitlab.net/dashb...## What does this MR do?
Fixes performance regression introduced after merging https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10462, after noticing performance degredation on `dev.gitlab.org`: https://performance.gitlab.net/dashboard/db/rails-controllers?orgId=1&from=now-7d&to=now&var-action=Projects::PipelinesController%23index.json&var-database=dev.gitlab.org.
The chosen solution: https://gitlab.com/gitlab-org/gitlab-ce/issues/27377#note_27110678
## What are the relevant issue numbers?
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/273779.1Kamil TrzcińśkiKamil Trzcińśkihttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10825Clusterize rendering of MR page2017-05-06T05:23:27Zusername-removed-408230Clusterize rendering of MR pagehttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10721Store latest in database for CI builds2017-05-05T11:07:04ZKamil TrzcińśkiStore latest in database for CI builds## What does this MR do?
This stores latest in the database. We update in transaction information about whether the build is latest. We don't need an index on that column, as we aim for 99% builds to be latest (retry is usually an except...## What does this MR do?
This stores latest in the database. We update in transaction information about whether the build is latest. We don't need an index on that column, as we aim for 99% builds to be latest (retry is usually an exception).
This greatly simplifies and fastens a lot of SQL queries and job-stage-related views.
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/257379.2yorickpeterse-stagingyorickpeterse-staginghttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10874Add index on ci_builds.user_id2017-04-27T03:32:56Zusername-removed-86853blackst0ne.ru@gmail.comAdd index on ci_builds.user_id## What does this MR do?
It adds an index on `ci_builds.user_id`.
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [x] Branch has no mer...## What does this MR do?
It adds an index on `ci_builds.user_id`.
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [x] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #312529.1yorickpeterse-stagingyorickpeterse-staginghttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10761Diff comment button debounce2017-04-25T19:03:32ZLuke "Jared" BennettDiff comment button debounce## What does this MR do?
~~Debounce the show, delay the hide and return early as possible for performance~~
Debounces the rendering of the comment button when `mouseover` a diff line.
Delays the hiding of the comment button when...## What does this MR do?
~~Debounce the show, delay the hide and return early as possible for performance~~
Debounces the rendering of the comment button when `mouseover` a diff line.
Delays the hiding of the comment button when `mouseleave` a diff line.
Returns as early as possible during the rendering/showing/hiding of the comment button to reduce wasted computation.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/304049.2Jacob SchatzJacob Schatzhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8410WIP: Resolve "Remove jQuery Nicescroll"2017-04-20T17:07:55ZLuke "Jared" BennettWIP: Resolve "Remove jQuery Nicescroll"## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #15664Luke "Jared" BennettLuke "Jared" Bennetthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10036WIP: improve GH importer performance2017-04-04T13:21:08ZJames LopezWIP: improve GH importer performanceImproves GH import performance
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_stylegu...Improves GH import performance
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?9.1James LopezJames Lopezhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10402Remove unnecessary eager load of project in milestone index2017-04-03T15:07:10ZStan HuRemove unnecessary eager load of project in milestone indexFound by Bullet in !10263 as seen in https://gitlab.com/gitlab-org/gitlab-ce/builds/13490762Found by Bullet in !10263 as seen in https://gitlab.com/gitlab-org/gitlab-ce/builds/134907629.1Robert SpeicherRobert Speicherhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/10385Add index on merge_requests.state2017-04-01T01:24:54Zusername-removed-840794Add index on merge_requests.state## What does this MR do?
Add index on merge_requests.state.
Example query - when visiting http://localhost:3000/gitlab-org/gitlab-test -:
```sql
SELECT COUNT(*) FROM "merge_requests" WHERE "merge_requests"."deleted_at" IS NULL AND "me...## What does this MR do?
Add index on merge_requests.state.
Example query - when visiting http://localhost:3000/gitlab-org/gitlab-test -:
```sql
SELECT COUNT(*) FROM "merge_requests" WHERE "merge_requests"."deleted_at" IS NULL AND "merge_requests"."target_project_id" = 1 AND ("merge_requests"."state" IN ('opened','reopened'));
```
Before the index - https://explain.depesz.com/s/EocWE:
```
QUERY PLAN
----------------------------------------------------------------------------------------------------------------------------
Aggregate (cost=135085.87..135085.88 rows=1 width=8) (actual time=487.182..487.182 rows=1 loops=1)
-> Seq Scan on merge_requests (cost=0.00..135085.87 rows=1 width=0) (actual time=0.320..487.174 rows=9 loops=1)
Filter: ((deleted_at IS NULL) AND ((state)::text = ANY ('{opened,reopened}'::text[])) AND (target_project_id = 1))
Rows Removed by Filter: 4006451
Planning time: 0.315 ms
Execution time: 487.221 ms
(6 rows)
```
After - https://explain.depesz.com/s/yl3q:
```
QUERY PLAN
----------------------------------------------------------------------------------------------------------------------------------------------------
Aggregate (cost=8.89..8.90 rows=1 width=8) (actual time=0.255..0.255 rows=1 loops=1)
-> Index Scan using index_merge_requests_on_state on merge_requests (cost=0.43..8.89 rows=1 width=0) (actual time=0.203..0.251 rows=9 loops=1)
Index Cond: ((state)::text = ANY ('{opened,reopened}'::text[]))
Filter: ((deleted_at IS NULL) AND (target_project_id = 1))
Rows Removed by Filter: 31
Planning time: 0.431 ms
Execution time: 0.358 ms
```
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [x] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added, if necessary
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9297WIP: Add index for slow queries in BuildsController#index2017-03-23T21:12:58ZStan HuWIP: Add index for slow queries in BuildsController#indexThe worst queries in loading this page looked like this:
```
SELECT COUNT("ci_builds"."id") FROM "ci_builds" WHERE "ci_builds"."type" IN ('Ci::Build') AND "ci_builds"."gl_project_id" = $1 AND ("ci_builds"."status" != $2) [["gl_proje...The worst queries in loading this page looked like this:
```
SELECT COUNT("ci_builds"."id") FROM "ci_builds" WHERE "ci_builds"."type" IN ('Ci::Build') AND "ci_builds"."gl_project_id" = $1 AND ("ci_builds"."status" != $2) [["gl_project_id", 10], ["status", "created"]]
```
This led to a bitmap heap scan that took 6-7 seconds in production.
Closes #273899.0Stan HuStan Huhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9962Fetch GH PR source refs in bulk2017-03-17T09:44:32ZJames LopezFetch GH PR source refs in bulk## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?9.1James LopezJames Lopezhttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8191Allow SlackService while migrating2017-03-14T17:49:08Zusername-removed-443319Allow SlackService while migrating1. Make the existing migration converting SlackService ->
SlackNotificationService a no-op.
2. Allow SlackService as an alternative class name for
SlackNotificationService. This also means that `#to_param` returns
the same thing for ...1. Make the existing migration converting SlackService ->
SlackNotificationService a no-op.
2. Allow SlackService as an alternative class name for
SlackNotificationService. This also means that `#to_param` returns
the same thing for both classes, so the UI will work in either case.
3. Create a post-deployment migration to update the existing service
names in batches.
In a future release, we can remove the dummy SlackService class and migrate any other data from SlackService -> SlackNotificationService.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/25843.8.15yorickpeterse-stagingyorickpeterse-staginghttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9772WIP: refactors branches finder code2017-03-13T16:24:19Zusername-removed-117638WIP: refactors branches finder code## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs....## What does this MR do?
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #273799.1username-removed-117638username-removed-117638https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5775Use pigz for increased backup and restore performance on multicore machines i...2017-02-06T17:52:28Zusername-removed-25949Use pigz for increased backup and restore performance on multicore machines if available## What does this MR do?
This MR enables the usage of pigz for creating and restoring backups if it is available on the machine.
On my PC this allowed ~70% faster packaging compared to gzip.
## Are there points in the code the reviewer ...## What does this MR do?
This MR enables the usage of pigz for creating and restoring backups if it is available on the machine.
On my PC this allowed ~70% faster packaging compared to gzip.
## Are there points in the code the reviewer needs to double check?
everything. It's a small change, but non working backup and restore would be bad.
## Why was this MR needed?
Currently the backup and restore task uses gzip which only runs on a single core, so it's pretty slow.
pigz is "A parallel implementation of gzip for modern
multi-processor, multi-core machines"
Information on pigz: http://www.zlib.net/pigz/
## What are the relevant issue numbers?
closes #20773
## Screenshots (if relevant)
-
## Does this MR meet the acceptance criteria?
- [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added
- [x] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
<strike>- [ ] API support added</strike>
- Tests
<strike>- [ ] Added for this feature/bug</strike>
- [x] All builds are passing
- [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [x] Branch has no merge conflicts with `master` (if you do - rebase it please)
- [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7728Add a Unicorn timeout logger to track down periodic 502 errors2017-01-25T06:37:03ZStan HuAdd a Unicorn timeout logger to track down periodic 502 errorsIf a Web request takes more than 60 s to process, Unicorn will kill the process and respawn it. We should log these slow requests.
Relates to https://gitlab.com/gitlab-com/infrastructure/issues/685If a Web request takes more than 60 s to process, Unicorn will kill the process and respawn it. We should log these slow requests.
Relates to https://gitlab.com/gitlab-com/infrastructure/issues/685yorickpeterse-stagingyorickpeterse-staginghttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8510Resolve "use jquery for all event listener registration"2017-01-15T22:37:51ZLuke "Jared" BennettResolve "use jquery for all event listener registration"## What does this MR do?
Adds https://gitlab.com/lbennett/eslint-plugin-turbolinks-event-handling eslint plugin.
Fixes linter errors.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## ...## What does this MR do?
Adds https://gitlab.com/lbennett/eslint-plugin-turbolinks-event-handling eslint plugin.
Fixes linter errors.
## Are there points in the code the reviewer needs to double check?
## Why was this MR needed?
## Screenshots (if relevant)
## Does this MR meet the acceptance criteria?
- [ ] [Changelog entry](https://docs.gitlab.com/ce/development/changelog.html) added
- [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)
- [ ] API support added
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html)
- [ ] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides)
- [ ] Branch has no merge conflicts with `master` (if it does - rebase it please)
- [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
## What are the relevant issue numbers?
Closes #264558.16Luke "Jared" BennettLuke "Jared" Bennetthttps://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6870WIP: Refactor discussion edit widget to have only one at a time.2016-12-28T18:41:36Zusername-removed-502136WIP: Refactor discussion edit widget to have only one at a time.Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/23227Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/23227username-removed-502136username-removed-502136https://staging.gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/386Follow on to MR3762016-11-22T16:40:22Zusername-removed-106671Follow on to MR376Follow-on to merge request 376 from @haynes : Remove unnecessary fetch of commit messages for initial push. This will reduce the memory usage significantly.Follow-on to merge request 376 from @haynes : Remove unnecessary fetch of commit messages for initial push. This will reduce the memory usage significantly.7.9username-removed-106671username-removed-106671