- 05 1月, 2018 1 次提交
-
-
由 Jan Provaznik 提交于
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
-
- 23 12月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
-
- 21 12月, 2017 1 次提交
-
-
由 Kim Carlbäcker 提交于
This reverts merge request !15712
-
- 19 12月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
Uses `list_commits_by_oid` on the CommitService, to request the needed commits for pipelines. These commits are needed to display the user that created the commit and the commit title. This includes fixes for tests failing that depended on the commit being `nil`. However, now these are batch loaded, this doesn't happen anymore and the commits are an instance of BatchLoader.
-
- 14 12月, 2017 3 次提交
-
-
由 haseeb 提交于
-
由 Jacopo 提交于
Allows ordering in GET api/v4/projects/:project_id/repository/contributors through `order_by` and `sort` params. The available `order_by` options are: name|email|commits. The available `sort` options are: asc|desc.
-
由 Ahmad Sherif 提交于
Closes gitaly#808
-
- 13 12月, 2017 1 次提交
-
-
由 Stan Hu 提交于
-
- 12 12月, 2017 1 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
- 07 12月, 2017 2 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Alejandro Rodríguez 提交于
-
- 01 12月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
This has the side effect of making this method rugged call free, which is the reason I actually changed this.
-
- 23 11月, 2017 3 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Lin Jen-Shin 提交于
-
- 22 11月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 21 11月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
After installing a new gem, batch-loader, a construct can be used to queue data to be fetched in bulk. The gem was also introduced in both gitlab-org/gitlab-ce!14680 and gitlab-org/gitlab-ce!14846, but those mrs are not merged yet. For the generation of diffs, both the old blob and the new blob need to be loaded. This for every file in the diff, too. Now we collect all these so we do 1 fetch. Three `.allow_n_plus_1_calls` have been removed, which I expect to be valid, but this needs to be confirmed by a full CI run. Possibly closes: - https://gitlab.com/gitlab-org/gitlab-ce/issues/37445 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37599 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37431
-
- 18 11月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
Conflicts used to take a `Repository` and pass that to `Gitlab::Highlight.highlight`, which would call `#gitattribute` on the repository. Now they use a `Gitlab::Git::Repository`, which didn't have that method defined - but defining it on `Gitlab::Git::Repository` does make it available on `Repository` through `method_missing`, so we can do that and both cases will work.
-
- 17 11月, 2017 1 次提交
-
-
由 Jacopo 提交于
Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses.
-
- 16 11月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This adds an optimised way of getting the latest pipeline status for a list of Commit objects (or just a single one).
-
- 10 11月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-
- 08 11月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
Prior to this MR there were two GitHub related importers: * Github::Import: the main importer used for GitHub projects * Gitlab::GithubImport: importer that's somewhat confusingly used for importing Gitea projects (apparently they have a compatible API) This MR renames the Gitea importer to Gitlab::LegacyGithubImport and introduces a new GitHub importer in the Gitlab::GithubImport namespace. This new GitHub importer uses Sidekiq for importing multiple resources in parallel, though it also has the ability to import data sequentially should this be necessary. The new code is spread across the following directories: * lib/gitlab/github_import: this directory contains most of the importer code such as the classes used for importing resources. * app/workers/gitlab/github_import: this directory contains the Sidekiq workers, most of which simply use the code from the directory above. * app/workers/concerns/gitlab/github_import: this directory provides a few modules that are included in every GitHub importer worker. == Stages The import work is divided into separate stages, with each stage importing a specific set of data. Stages will schedule the work that needs to be performed, followed by scheduling a job for the "AdvanceStageWorker" worker. This worker will periodically check if all work is completed and schedule the next stage if this is the case. If work is not yet completed this worker will reschedule itself. Using this approach we don't have to block threads by calling `sleep()`, as doing so for large projects could block the thread from doing any work for many hours. == Retrying Work Workers will reschedule themselves whenever necessary. For example, hitting the GitHub API's rate limit will result in jobs rescheduling themselves. These jobs are not processed until the rate limit has been reset. == User Lookups Part of the importing process involves looking up user details in the GitHub API so we can map them to GitLab users. The old importer used an in-memory cache, but this obviously doesn't work when the work is spread across different threads. The new importer uses a Redis cache and makes sure we only perform API/database calls if absolutely necessary. Frequently used keys are refreshed, and lookup misses are also cached; removing the need for performing API/database calls if we know we don't have the data we're looking for. == Performance & Models The new importer in various places uses raw INSERT statements (as generated by `Gitlab::Database.bulk_insert`) instead of using Rails models. This allows us to bypass any validations and callbacks, drastically reducing the number of SQL queries and Gitaly RPC calls necessary to import projects. To ensure the code produces valid data the corresponding tests check if the produced rows are valid according to the model validation rules.
-
- 06 11月, 2017 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 04 11月, 2017 3 次提交
-
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
由 Alejandro Rodríguez 提交于
-
- 03 11月, 2017 1 次提交
-
-
由 micael.bergeron 提交于
also, I refactored the MergeRequest#fetch_ref method to express the side-effect that this method has. MergeRequest#fetch_ref -> MergeRequest#fetch_ref! Repository#fetch_source_branch -> Repository#fetch_source_branch!
-
- 27 10月, 2017 2 次提交
-
-
由 Lin Jen-Shin (godfat) 提交于
-
由 Zeger-Jan van de Weg 提交于
Now, when requesting a commit from the Repository model, the results are not cached. This means we're fetching the same commit by oid multiple times during the same request. To prevent us from doing this, we now cache results. Caching is done only based on object id (aka SHA). Given we cache on the Repository model, results are scoped to the associated project, eventhough the change of two repositories having the same oids for different commits is small.
-
- 25 10月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
We also delete some unused code related to the aforementioned feature.
-
- 20 10月, 2017 1 次提交
-
-
由 Alejandro Rodríguez 提交于
This saves us Rugged/gRPC invocations
-
- 16 10月, 2017 1 次提交
-
-
由 Andrew Newdigate 提交于
-
- 13 10月, 2017 2 次提交
-
-
由 Alejandro Rodríguez 提交于
This prepares the codebase for a Gitaly migration. See https://gitlab.com/gitlab-org/gitaly/issues/553
-
由 Alejandro Rodríguez 提交于
-
- 12 10月, 2017 2 次提交
-
-
由 Brett Walker 提交于
threshhold, a message is shown indicating we didn't perform the search
-
由 Sean McGivern 提交于
We were looking these up on each request to an issue page, because the form is pre-filled, as is the template dropdown. That was unnecessary: we could just treat these as 'special' repository files (like the rendered README) and cache them in Redis until they change on a push.
-
- 11 10月, 2017 1 次提交
-
-
由 Brett Walker 提交于
the long running git query
-
- 04 10月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 02 10月, 2017 1 次提交
-
-
由 Stan Hu 提交于
`Repository#has_visible_content?` used to rely on the cached count of local branches, but since it is now an independently cached value it needs to be invalidated on its own. Closes #38646
-
- 29 9月, 2017 1 次提交
-
-
由 Jacob Vosmaer (GitLab) 提交于
-