- 29 10月, 2016 1 次提交
-
-
由 Guilherme Salazar 提交于
fix issues pointed out in !6527 add task completion status feature to CHANGELOG
-
- 25 10月, 2016 1 次提交
-
-
由 David Wagner 提交于
They were Rails' default and are unnecessarily overridden. Signed-off-by: NDavid Wagner <david@marvid.fr>
-
- 20 10月, 2016 4 次提交
-
-
由 Nick Thomas 提交于
-
由 Nick Thomas 提交于
-
由 Nick Thomas 提交于
This reverts commit 31c37c6c. See #23341
-
-
- 18 10月, 2016 3 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 14 10月, 2016 6 次提交
-
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
由 Z.J. van de Weg 提交于
-
由 Sean McGivern 提交于
When reading conflicts: 1. Add a `type` field. `text` works as before, and has `sections`; `text-editor` is a file with ambiguous conflict markers that can only be resolved in an editor. 2. Add a `content_path` field pointing to a JSON representation of the file's content for a single file. 3. Hitting `content_path` returns a similar datastructure to the `file`, but without the `content_path` and `sections` fields, and with a `content` field containing the full contents of the file (with conflict markers). When writing conflicts: 1. Instead of `sections` being at the top level, they are now in a `files` array. This matches the read format better. 2. The `files` array contains file hashes, each of which must contain: a. `new_path` b. `old_path` c. EITHER `sections` (which works as before) or `content` (with the full content of the resolved file).
- 06 10月, 2016 1 次提交
-
-
由 Paco Guzman 提交于
-
- 04 10月, 2016 1 次提交
-
-
由 Felipe Artur 提交于
-
- 03 10月, 2016 1 次提交
-
-
由 Thomas Balthazar 提交于
It toggles the 'WIP' prefix in the MR title.
-
- 27 9月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
Now a merge request with a blank description will no longer produce a merge commit message like this: ``` Merge branch 'foo' into 'master' Bring the wonders of foo into the world See merge request !7283 ``` What an improvement!
🎉
-
- 21 9月, 2016 4 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
- For target project show only environments for target branch or with tags - For source project show only environments for source branch
-
由 Timothy Andrew 提交于
- Instead of overriding `create` and `update` in `MergeRequests::BaseService` - Get all merge request service specs passing
-
由 Timothy Andrew 提交于
- Don't use `TableReferences` - using `.arel_table` is shorter! - Move some database-related code to `Gitlab::Database` - Remove the `MergeRequest#issues_closed` and `Issue#closed_by_merge_requests` associations. They were either shadowing or were too similar to existing methods. They are not being used anywhere, so it's better to remove them to reduce confusion. - Use Rails 3-style validations - Index for `MergeRequest::Metrics#first_deployed_to_production_at` - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that need it. - Other minor refactorings.
-
- 20 9月, 2016 6 次提交
-
-
由 Timothy Andrew 提交于
- Move things common to `Issue` and `MergeRequest` into `Issuable` - Move more database-specific functions into `Gitlab::Database` - Indentation changes and other minor refactorings.
-
由 Lin Jen-Shin 提交于
However, if MergeRequest#all_commits_sha would want to handle non-persisted merge request, by judging its name, it should not just give 1 SHA, but all of them. But we don't really care all_commits_sha for non-persisted merge request anyway. So I think we should just ignore that case. Better to not implementing something than implementing it in a wrong and confusing way.
-
由 Timothy Andrew 提交于
-
由 Timothy Andrew 提交于
1. Change multiple updates to a single `update_all` 2. Use cascading deletes 3. Extract an average function for the database median. 4. Move database median to `lib/gitlab/database` 5. Use `delete_all` instead of `destroy_all` 6. Minor refactoring
-
- 19 9月, 2016 4 次提交
-
-
由 Lin Jen-Shin 提交于
This way we could also show pipelines from commits which were discarded due to a force push.
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
Environments that can have a URL with predefined CI variables.
-
由 Timothy Andrew 提交于
All the code that pre-calculates metrics for use in the cycle analytics page. - Ci::Pipeline -> build start/finish - Ci::Pipeline#merge_requests - Issue -> record default metrics after save - MergeRequest -> record default metrics after save - Deployment -> Update "first_deployed_to_production_at" for MR metrics - Git Push -> Update "first commit mention" for issue metrics - Merge request create/update/refresh -> Update "merge requests closing issues"
-
- 16 9月, 2016 1 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 15 9月, 2016 1 次提交
-
-
由 Timothy Andrew 提交于
1. These changes bring down page load time for 100 issues from more than a minute to about 1.5 seconds. 2. This entire commit is composed of these types of performance enhancements: - Cache relevant data in `IssueMetrics` wherever possible. - Cache relevant data in `MergeRequestMetrics` wherever possible. - Preload metrics 3. Given these improvements, we now only need to make 4 SQL calls: - Load all issues - Load all merge requests - Load all metrics for the issues - Load all metrics for the merge requests 4. A list of all the data points that are now being pre-calculated: a. The first time an issue is mentioned in a commit - In `GitPushService`, find all issues mentioned by the given commit using `ReferenceExtractor`. Set the `first_mentioned_in_commit_at` flag for each of them. - There seems to be a (pre-existing) bug here - files (and therefore commits) created using the Web CI don't have cross-references created, and issues are not closed even when the commit title is "Fixes #xx". b. The first time a merge request is deployed to production When a `Deployment` is created, find all merge requests that were merged in before the deployment, and set the `first_deployed_to_production_at` flag for each of them. c. The start / end time for a merge request pipeline Hook into the `Pipeline` state machine. When the `status` moves to `running`, find the merge requests whose tip commit matches the pipeline, and record the `latest_build_started_at` time for each of them. When the `status` moves to `success`, record the `latest_build_finished_at` time. d. The merge requests that close an issue - This was a big cause of the performance problems we were having with Cycle Analytics. We need to use `ReferenceExtractor` to make this calculation, which is slow when we have to run it on a large number of merge requests. - When a merge request is created, updated, or refreshed, find the issues it closes, and create an instance of `MergeRequestsClosingIssues`, which acts as a join model between merge requests and issues. - If a `MergeRequestsClosingIssues` instance links a merge request and an issue, that issue closes that merge request. 5. The `Queries` module was changed into a class, so we can cache the results of `issues` and `merge_requests_closing_issues` across various cycle analytics stages. 6. The code added in this commit is untested. Tests will be added in the next commit.
-
- 13 9月, 2016 5 次提交
-
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-
由 Katarzyna Kobierska 提交于
-