- 01 6月, 2018 1 次提交
-
-
由 Mark Chao 提交于
"Maintainer" will be freed to be used for #42751
-
- 29 5月, 2018 1 次提交
-
-
由 blackst0ne 提交于
-
- 03 5月, 2018 1 次提交
-
-
由 Winnie Hellmann 提交于
-
- 11 4月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
So we can distinguish between the permissions on the source and the target project. - `create_merge_request_from` indicates a user can create a merge request with the project as a source_project - `create_merge_request_in` indicates a user can create a merge request with the project as a target_project
-
- 07 3月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
When a project is not private, and the source branch not protected the user can now select the option to allow maintainers to push to this branch
-
- 23 2月, 2018 1 次提交
-
-
由 Bob Van Landuyt 提交于
-
- 02 2月, 2018 1 次提交
-
-
由 Yorick Peterse 提交于
This ensures that we have more visibility in the number of SQL queries that are executed in web requests. The current threshold is hardcoded to 100 as we will rarely (maybe once or twice) change it. In production and development we use Sentry if enabled, in the test environment we raise an error. This feature is also only enabled in production/staging when running on GitLab.com as it's not very useful to other users.
-
- 15 1月, 2018 1 次提交
-
-
由 Felipe Artur 提交于
-
- 12 1月, 2018 1 次提交
-
-
由 🙈 jacopo beschi 🙉 提交于
-
- 14 12月, 2017 1 次提交
-
-
由 Ahmad Sherif 提交于
Closes gitaly#808
-
- 07 12月, 2017 4 次提交
-
-
由 micael.bergeron 提交于
-
由 micael.bergeron 提交于
-
由 micael.bergeron 提交于
add a spec for commit merge request diff notes
-
由 Douwe Maan 提交于
-
- 29 11月, 2017 2 次提交
-
-
由 Sean McGivern 提交于
If a merge request was created with a branch name that also matched a tag name, we'd generate a comparison to or from the tag respectively, rather than the branch. Merging would still use the branch, of course. To avoid this, ensure that when we get the branch heads, we prepend the reference prefix for branches, which will ensure that we generate the correct comparison.
-
由 Sean McGivern 提交于
The st_commits and st_diffs columns on merge_request_diffs historically held the YAML-serialised data for a merge request diff, in a variety of formats. Since 9.5, these have been migrated in the background to two new tables: merge_request_diff_commits and merge_request_diff_files. That has the advantage that we can actually query the data (for instance, to find out how many commits we've stored), and that it can't be in a variety of formats, but must match the new schema. This is the final step of that journey, where we drop those columns and remove all references to them. This is a breaking change to the importer, because we can no longer import diffs created in the old format, and we cannot guarantee the export will be in the new format unless it was generated after this commit.
-
- 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
-
- 08 11月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
Use Commit#notes and Note.for_commit_id when possible to make sure we use all the indexes available to us
-
- 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!
-
- 13 10月, 2017 2 次提交
-
-
由 Alejandro Rodríguez 提交于
Rename classes to (hopefully) clearer names while we're doing that.
-
由 Alejandro Rodríguez 提交于
This prepares the codebase for a Gitaly migration. See https://gitlab.com/gitlab-org/gitaly/issues/553
-
- 07 10月, 2017 2 次提交
-
-
由 Bob Van Landuyt 提交于
-
由 Toon Claes 提交于
In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo secondary node). But in GitLab CE it also might be useful to have the "read-only" idea around. So port it back to GitLab CE. Also having the principle of read-only in GitLab CE would hopefully lead to less errors introduced, doing write operations when there aren't allowed for read-only calls. Closes gitlab-org/gitlab-ce#37534.
-
- 19 9月, 2017 1 次提交
-
-
由 Andrew Newdigate 提交于
-
- 14 9月, 2017 1 次提交
-
-
由 Jarka Kadlecova 提交于
-
- 07 9月, 2017 1 次提交
-
-
由 Tiago Botelho 提交于
-
- 06 9月, 2017 2 次提交
-
-
由 Tiago Botelho 提交于
-
由 micael.bergeron 提交于
this will remove the need make N queries (per-note) at the cost of having to mark notes with an attribute this opens up the possibility for other special roles for notes
-
- 14 7月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 07 7月, 2017 2 次提交
-
-
由 Luke "Jared" Bennett 提交于
-
由 Luke "Jared" Bennett 提交于
Removed merge_request/issue state_event param parent and removed issuable_path helpers in favour of issuable_url helpers
-
- 06 7月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 29 6月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-