summaryrefslogtreecommitdiff
path: root/spec/services
Commit message (Collapse)AuthorAgeFilesLines
* Check the HEAD of branch when doing Merge When Succeededimprove-merge-when-succeededKamil Trzcinski2016-02-221-0/+16
|
* Merge branch 'tasks' into 'master' Douglas Barbosa Alexandre2016-02-229-4/+530
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add Todos Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/2425 Tasks: - Prepare database - [X] Create a new table (`todos`) - Tasks Queue view - [X] Add a number icon showing the number of todos on the top right next to the new and logout button that will redirect the user to the todos page - [X] Add a chronological list of todos, with the 'Todos' tab active by default - [X] Add a 'Done' button to each todo - [x] Add filters (project, author, type, and action) - Todos generation - [X] When user issue/mr is assgined to someone - [x] When user is mentioned on (issues/mr's/comments) - Mark todo as `done` - [X] When clicks on the 'Done' button - [X] When edit issue/mr - [X] When left/edit a comment - [X] When reassign issue/mr - [X] When add/remove labels to issue/mr - [X] When issue/mr is closed - [X] When mr is merged - [X] When added an emoji - [X] When changed the issue/mr milestone * Screenshot: ![Screenshot_2016-02-20_12.45.57](/uploads/4b2554b1bde25aed3347e1ae41e8e0c0/Screenshot_2016-02-20_12.45.57.png) See merge request !2817
| * Rename Tasks to TodosDouglas Barbosa Alexandre2016-02-209-322/+327
| |
| * Create or mark task pending as soon the action happensDouglas Barbosa Alexandre2016-02-201-1/+1
| |
| * Ensure that we only have one task per issue/mrDouglas Barbosa Alexandre2016-02-201-18/+16
| |
| * Explicit mention of the assignee make a taskDouglas Barbosa Alexandre2016-02-201-4/+4
| | | | | | | | Since potentially the previous assign-task has already been handled.
| * Fix rubocop offensesDouglas Barbosa Alexandre2016-02-201-3/+3
| |
| * Create a pending task when a user is mentioned when edit a issue/mr/noteDouglas Barbosa Alexandre2016-02-206-79/+76
| |
| * Does not create a task if new assignee is the current userDouglas Barbosa Alexandre2016-02-201-0/+12
| |
| * Create a pending task when a user is mentioned on a noteDouglas Barbosa Alexandre2016-02-201-0/+11
| |
| * Create a pending task when a user is mentioned on issue/mrDouglas Barbosa Alexandre2016-02-201-30/+66
| |
| * Rename TaskService#mark_as_done to mark_pending_tasks_as_doneDouglas Barbosa Alexandre2016-02-201-2/+2
| |
| * Marks pending tasks for an user as done when he merge the MRDouglas Barbosa Alexandre2016-02-201-0/+17
| |
| * Marks pending tasks for an user as done when he close the MRDouglas Barbosa Alexandre2016-02-202-0/+24
| |
| * Marks pending tasks for an user as done when he edit a MRDouglas Barbosa Alexandre2016-02-201-1/+54
| |
| * Create a pending task when an MR is assigned to someoneDouglas Barbosa Alexandre2016-02-203-8/+109
| |
| * Mark pending tasks for the current user as done when he edit a noteDouglas Barbosa Alexandre2016-02-201-0/+45
| |
| * Mark pending tasks for the note author as done when he left a noteDouglas Barbosa Alexandre2016-02-202-4/+40
| |
| * Marks pending tasks for an user as done when he close the issueDouglas Barbosa Alexandre2016-02-202-0/+25
| |
| * Marks pending tasks for an user as done when he edit an issueDouglas Barbosa Alexandre2016-02-202-11/+83
| |
| * Does not create a task for new issue when assignee is the current userDouglas Barbosa Alexandre2016-02-201-0/+4
| |
| * Create a pending task when an issue is assigned to someoneDouglas Barbosa Alexandre2016-02-203-2/+92
| |
* | Discover branches for commit statuses ref-less when doing merge when succeededmerge-when-succeededKamil Trzcinski2016-02-191-6/+30
| |
* | Fix Merge When Succeeded for multiple stagesKamil Trzcinski2016-02-191-0/+30
|/ | | | Use around_transition to trigger build creation for next stages
* Merge branch 'fix/ci-first-job-allow-failure' into 'master' Kamil Trzciński2016-02-181-0/+28
|\ | | | | | | | | | | | | | | | | Fix CI builds scheduler when first build in stage is allowed to fail This fixes an edge case in CI builds scheduler when first build in stage was marked as allowed to fail. Closes #3192 See merge request !2869
| * Add specs for build status helper classGrzegorz Bizon2016-02-181-3/+11
| |
| * Return a builds array in builds create serviceGrzegorz Bizon2016-02-181-0/+20
| |
* | Merge branch 'fix/gitpushservice-complexity-issue' into 'master' Douwe Maan2016-02-181-32/+41
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | Reduce code complexity on GitPushService#execute Code complexity for gitlab-ce after this has been refactored: ``` 27.3: GitPushService#execute ``` This still needs to be merged into `gitlab-ee` presumably with conflicts... Perhaps we should create another issue for doing that? I left the code sort of similar to what it was... If I could, I would have refactored most of the code into separate classes, etc. as it breaks probably all SOLID principles. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/13327 See merge request !2784
| * refactored specJames Lopez2016-02-171-9/+12
| |
| * refactored some stuff based on MR feedbackJames Lopez2016-02-171-54/+30
| |
| * refactored GitPushService and updated specJames Lopez2016-02-151-24/+24
| |
| * attempt to reduce code complexity on GitPushService#executeJames Lopez2016-02-111-26/+56
| |
* | Merge branch 'master' of https://gitlab.com/gitlab-org/gitlab-ce into ↵Jacob Vosmaer2016-02-172-0/+45
|\ \ | | | | | | | | | git-archive-refactor
| * | updated system note service and spec based on feedbackJames Lopez2016-02-161-4/+0
| | |
| * | fix rubocop warningJames Lopez2016-02-121-2/+4
| | |
| * | woo hoo - getting there with the cross-reference issue. Should fix the ↵James Lopez2016-02-121-4/+6
| | | | | | | | | | | | problem and updated spec
| * | Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into ↵James Lopez2016-02-101-0/+30
| |\ \ | | |/ | | | | | | fix/cross-reference-notes-forks
| | * Smarter flushing of branch statistics cachesYorick Peterse2016-02-091-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of flushing the behind/ahead counts for all branches upon every push we now only flush the cache of branches that actually need to have these statistics recalculated. There are now basically 2 scenarios and their effects: 1. A user pushes a commit to the default branch, this results in the cache being flushed for all branches. 2. A user pushes to a non default branch, this results in _only_ the cache for that branch being flushed. The existing code (Repository#expire_cache) remains backwards compatible with the previous behaviour, the new behaviour is only applied when a branch name is passed as an argument. This ensures that when for example a project is deleted the cache for all branches is flushed.
| | * Cache various Repository Git operationscaching-repository-git-operationsYorick Peterse2016-02-081-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This caches the output of the following methods: * Repository#empty? * Repository#has_visible_content? * Repository#root_ref The cache for Repository#has_visible_content? is flushed whenever a commit is pushed to a new branch or an existing branch is removed. The cache for Repository#root_ref is only flushed whenever a user changes the default branch of a project. The cache for Repository#empty? is never explicitly flushed as there's no need for it.
| * | fixed spec - at last!James Lopez2016-02-051-3/+2
| | |
| * | WIP - fix and spec for cross reference issue with forksJames Lopez2016-02-041-0/+16
| |/
* | First version of "git archive" headersJacob Vosmaer2016-02-021-25/+0
|/
* Fix Rubocop errornote-background-jobJosh Frye2016-01-281-3/+3
|
* Update testsJosh Frye2016-01-282-3/+27
|
* Extract Projects::ImportService service from RepositoryImportWorkerDouglas Barbosa Alexandre2016-01-251-0/+106
|
* Use a MR with commits.Rubén Dávila2016-01-201-1/+1
|
* Fix creator should be added as a master of the project on creationDouglas Barbosa Alexandre2016-01-191-0/+1
|
* This will ensure previous assignee gets an email even if his notif level is ↵fix-consider-re-assign-as-a-mentionRémy Coutable2016-01-151-0/+40
| | | | "on mention"
* Consider re-assign as a mention from a notification point of viewRémy Coutable2016-01-151-1/+17
| | | | | This will ensure new assignee gets an email even if his notif level is "on mention".
* Merge branch 'feature/ldap-sync-edgecases' into 'master' Douwe Maan2016-01-141-0/+23
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | LDAP Sync blocked user edgecases Allow GitLab admins to block otherwise valid GitLab LDAP users (https://gitlab.com/gitlab-org/gitlab-ce/issues/3462) Based on the discussion on the original issue, we are going to differentiate "normal" block operations to the ldap automatic ones in order to make some decisions when its one or the other. Expected behavior: - [x] "ldap_blocked" users respond to both `blocked?` and `ldap_blocked?` - [x] "ldap_blocked" users can't be unblocked by the Admin UI - [x] "ldap_blocked" users can't be unblocked by the API - [x] Block operations that are originated from LDAP synchronization will flag user as "ldap_blocked" - [x] Only "ldap_blocked" users will be automatically unblocked by LDAP synchronization - [x] When LDAP identity is removed, we should convert `ldap_blocked` into `blocked` Mockup for the Admin UI with both "ldap_blocked" and normal "blocked" users: ![image](/uploads/4f56fc17b73cb2c9e2a154a22e7ad291/image.png) There will be another MR for the EE version. See merge request !2242
View Lorry Controller Status