- 05 9月, 2019 1 次提交
-
-
由 Eugenia Grieff 提交于
- Add new service that transfers milestones from a group to a project - Include new service in Projects transfer service - Include FromUnion module in Milestone model to use in transfer service - Add specs for new milestones service - Add specs for transferring milestones in project transfer service
-
- 04 9月, 2019 3 次提交
-
-
由 Oswaldo Ferreira 提交于
-
由 dineshpanda 提交于
-
由 Jan Provaznik 提交于
Creates new event when an epic is created, closed, reopened or commented.
-
- 03 9月, 2019 4 次提交
-
-
由 Etienne Baqué 提交于
Modified schema via migrations. Added one-to-one relationship between the two models. Added changelog file
-
由 Giorgenes Gelatti 提交于
Extends the permission of $CI_REGISTRY_USER to allow them to delete tags in addition to just pushing. https://gitlab.com/gitlab-org/gitlab-ce/issues/40096
-
由 Brandon Williams 提交于
When updating group and project members, new system hooks `user_update_for_group` and `user_update_for_team` will be executed. Fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/12252
-
由 Sean McGivern 提交于
The 'assigned' reason doesn't apply to notes, but the other two can ('mentioned' and 'own_activity'), so we can still use this for note emails.
-
- 02 9月, 2019 1 次提交
-
-
由 Maneschi Romain 提交于
-
- 31 8月, 2019 1 次提交
-
-
由 Manoj MJ 提交于
This change limits the number of emails for new access requests notifications to 10 most recently active owners/maintainers
-
- 30 8月, 2019 3 次提交
-
-
由 Tiger 提交于
Feature flag has been defaulting to `true` since 12.2
-
由 Alex Kalderimis 提交于
This allows the be_url matcher to be more specific. By default, it only matches HTTP and HTTPS URIs.
-
由 João Cunha 提交于
Extract duplicated code from two similar classes into a parent one.
-
- 29 8月, 2019 3 次提交
-
-
由 Stan Hu 提交于
When a restricted visibility level of `private` is set in the instance, creating a snippet with the `visibility` level would always fail. This happened because: 1. `params[:visibility]` was a string (e.g. "public") 2. `CreateSnippetService` and `UpdateSnippetService` only looked at `params[:visibility_level]`, which was `nil`. To fix this, we: 1. Make `CreateSnippetService` look at the newly-built `snippet.visibility_level`, since the right value is assigned by the `VisibilityLevel#visibility=` method. 2. Modify `UpdateSnippetService` to handle both `visibility_level` and `visibility` parameters. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66050
-
由 Sean McGivern 提交于
-
由 Felipe Artur 提交于
Persists if a board list is collapsed for each user.
-
- 28 8月, 2019 3 次提交
-
-
由 Tiger 提交于
These services aren't specific to GCP, and will be used for AWS as part of https://gitlab.com/gitlab-org/gitlab-ce/issues/46686
-
由 Stan Hu 提交于
During a project import, `LfsLinkService` attempts to link `LfsObjects` that have not already been associated with a project. It's possible for a large repo to have thousands of OIDs, which can cause long database query and parsing times. By processing a batch of 1000 at a time, we can reduce that time at the expense of a few more SQL queries. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66274
-
由 Luke Duncalfe 提交于
Notes call `#after_note_created` and `#after_note_destroyed` on their noteable in callbacks, so the noteable can perform tasks particular to them, like cache expiry. This is in preparation of the EE-specific class `DesignManagement::Design` clearing its `user_notes_count` cache when its note are created or destroyed. Refactoring Rspec behaviour testing of a counter caching service into a shared example. https://gitlab.com/gitlab-org/gitlab-ee/issues/13353
-
- 27 8月, 2019 3 次提交
-
-
由 Aishwarya Subramanian 提交于
-
由 Aishwarya Subramanian 提交于
-
由 Aishwarya Subramanian 提交于
-
- 26 8月, 2019 2 次提交
-
-
由 Igor 提交于
Code Review Usage Ping for Create SMAU
-
由 Patrick Derichs 提交于
Call QuickActionsService on Note update Add support for notes which just contain commands after editing Return http status gone (410) if note was deleted Temporary frontend addition so it is not failing when a note is deleted Move specs to shared examples Fix rubocop style issue Deleting note on frontend when status is 410 Use guard clause for note which got deleted Simplified condition for nil note This method should no longer be called with nil note Refactoring of execute method to reduce complexity Move errors update to delete_note method Note is now deleted visually when it only contains commands after update Add expectation Fix style issues Changing action to fix tests Add tests for removeNote and update deleteNote expectations
-
- 24 8月, 2019 2 次提交
-
-
由 Brett Walker 提交于
User images and videos will get proxied through the Camo server in order to keep malicious sites from collecting the IP address of users.
-
由 Reuben Pereira 提交于
Add to the service and migration both.
-
- 23 8月, 2019 2 次提交
-
-
由 Nick Thomas 提交于
At present, the TodoService uses the `:read_project` ability to decide whether a user can read a note on a commit. However, commits can have a visibility level that is more restricted than the project, so this is a security issue. This commit changes the code to use the `:read_commit` ability in this case instead, which ensures TODOs are only generated for commit notes if the users can see the commit.
-
由 Robert Schilling 提交于
-
- 22 8月, 2019 3 次提交
-
-
由 Robert Schilling 提交于
-
由 Kamil Trzciński 提交于
This makes BuildQueueService to force refresh runners that are considered to have recent queue. Such runners are the ones that connected within online interval + time to expire runner cache.
-
由 Heinrich Lee Yu 提交于
-
- 21 8月, 2019 3 次提交
-
-
由 Fabio Pitino 提交于
This is a port from EE changes where we introduce a new limit for Plan model. https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/1182
-
由 Luke Duncalfe 提交于
Adding, destroying and toggling emoji previously lacked services and instead were performed through methods called on Awardable models. This led to inconsistencies where relevant todos would be marked as done only when emoji were awarded through our controllers, but not through the API. Todos could also be marked as done when an emoji was being removed. Behaviour changes - Awarding emoji through the API will now mark a relevant Todo as done - Toggling an emoji off (destroying it) through our controllers will no longer mark a relevant Todo as done Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63372
-
由 Luke Duncalfe 提交于
This finder class acts more as a service, as it only returns mapped data. Renaming this class allows us to create a new AwardEmojiFinder without the ambiguity of there being two similarly-named finders. https://gitlab.com/gitlab-org/gitlab-ce/issues/63372
-
- 18 8月, 2019 1 次提交
-
- 17 8月, 2019 3 次提交
-
-
由 Stan Hu 提交于
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31741 introduced a regression where not all the right parameters would be passed into `Ci::CreatePipelineService`. We fix this by breaking out the pipeline parameters and reusing a method from `Gitlab::DataBuilder::Push`. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66196
-
由 Stan Hu 提交于
Previously `ProjectCacheWorker` would be scheduled once per ref, which would generate unnecessary I/O and load on Sidekiq, especially if many tags or branches were pushed at once. `ProjectCacheWorker` would expire three items: 1. Repository size: This only needs to be updated once per push. 2. Commit count: This only needs to be updated if the default branch is updated. 3. Project method caches: This only needs to be updated if the default branch changes, but only if certain files change (e.g. README, CHANGELOG, etc.). Because the third item requires looking at the actual changes in the commit deltas, we schedule one `ProjectCacheWorker` to handle the first two cases, and schedule a separate `ProjectCacheWorker` for the third case if it is needed. As a result, this brings down the number of `ProjectCacheWorker` jobs from N to 2. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52046
-
由 Douwe Maan 提交于
Instead of checking if a commit already exists in the upstream project in its ProcessCommitWorker and bailing out if it does, we check the existence of all commits in bulk in Git::BranchHooksService, so that we can skip scheduling ProcessCommitWorker jobs for those commits that already exist upstream entirely.
-
- 16 8月, 2019 2 次提交
-
-
由 Nick Thomas 提交于
Prior to 12.1, rebase status was looked up directly from Gitaly. In https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14417 , a DB column was added to track the status instead. However, we couldn't stop looking at the gitaly status immediately, since some rebases may been running across the upgrade. Now that we're in 12.3, it is safe to remove the direct-to-gitaly lookup. This also happens to fix a 500 error that is seen when viewing an MR for a fork where the source project has been removed. We still look at the Gitaly status in the service, just in case Gitaly and Sidekiq get out of sync - I assume this is possible, and it's a relatively cheap check. Since we atomically check and set `merge_requests.rebase_jid`, we should never enqueue two `RebaseWorker` jobs in parallel.
-
由 Brett Walker 提交于
- Adds UI to configure in group and project settings - Removes notification configuration for users when disabled at group or project level
-