summaryrefslogtreecommitdiff
path: root/spec/services/merge_requests/update_service_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Make guests unable to view MRsguests_cant_see_mrsValery Sizov2016-10-111-0/+6
|
* Add a spec for merge request metric caching while refreshing a merge request ↵Timothy Andrew2016-09-211-3/+6
| | | | from a forked project.
* Use the `IssuableBaseService` lifecycle hooks to cache ↵Timothy Andrew2016-09-211-3/+3
| | | | | | | `MergeRequestsClosingIssues` - Instead of overriding `create` and `update` in `MergeRequests::BaseService` - Get all merge request service specs passing
* Implement a second round of review comments from @DouweM.Timothy Andrew2016-09-211-3/+3
| | | | | | | | | | | | | | - 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.
* Fix rubocop spec.Timothy Andrew2016-09-201-1/+1
| | | | And `scss_lint`
* Test all cycle analytics pre-calculation code.Timothy Andrew2016-09-191-0/+34
| | | | | | | | | | | | | 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"
* DRY up the added update service specs, add two email helpersNick Thomas2016-08-161-31/+3
|
* Address minor review comments for testsNick Thomas2016-08-161-4/+4
|
* Add notifications for new user mentions in merge requestsNick Thomas2016-08-151-0/+33
|
* adds second batch of tests changed to active tenseactive-tense-test-coveragetiagonbotelho2016-08-091-4/+4
|
* Merge branch 'rm-source-branch' into 'master' Douwe Maan2016-05-201-1/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | Allows MR authors to have the source branch removed when merging the MR closes #13191 The location of the checkbox might not be optimal so any feedback is welcome. Any other feedback too obviously. Screenshot: ![Screenshot_2016-02-17_21.25.24](/uploads/a9c3eaafb39c6f5b4f0949a2278af6da/Screenshot_2016-02-17_21.25.24.png) See merge request !2801
| * Allows MR authors to have the source branch removed when merging the MRJeroen Jacobs2016-05-201-1/+3
| |
* | Create DiffFilter and change SystemNoteService#change_title to use ↵Adam Butler2016-05-181-2/+2
|/ | | | Gitlab::Diff::InlineDiff
* Update specs to accomodate issuable assign changesGrzegorz Bizon2016-04-221-3/+8
|
* Improving the original label-subscribing implementationRémy Coutable2016-03-151-33/+22
| | | | | | | 1. Make the "subscribed" text in Issuable sidebar reflect the labels subscription status 2. Current user mut be logged-in to toggle issue/MR/label subscription
* Original implementation to allow users to subscribe to labelsTimothy Andrew2016-03-151-1/+55
| | | | | | | | | | | | | | | | | | 1. Allow subscribing (the current user) to a label - Refactor the `Subscription` coffeescript class - The main change is that it accepts a container, and conducts all DOM queries within its scope. We need this because the labels page has multiple instances of `Subscription` on the same page. 2. Creating an issue or MR with labels notifies users subscribed to those labels - Label `has_many` subscribers through subscriptions. 3. Adding a label to an issue or MR notifies users subscribed to those labels - This only applies to subscribers of the label that has just been added, not all labels for the issue.
* Rename Tasks to TodosDouglas Barbosa Alexandre2016-02-201-18/+19
|
* Create a pending task when a user is mentioned when edit a issue/mr/noteDouglas Barbosa Alexandre2016-02-201-3/+1
|
* 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-201-0/+25
|
* Tag service specsDouwe Maan2015-12-091-1/+1
|
* test fixValery Sizov2015-11-301-2/+4
|
* Generate system note after Task item has been updated on Issue or Merge ↵Ruben Davila2015-11-191-6/+45
| | | | | | | | | | | | Request. #2296 Everytime the User check or uncheck a Task Item from the Issue or Merge Request description, a new update is going to be added to the activity logs of the Issue or Merge Request. Note that when using the edit form, you can only update the Task item status or add/delete/modify existing ones. Doing both actions is not fully supported.
* Add tests for merge request update.Douwe Maan2015-11-171-4/+7
|
* Support editing target branch of merge requestStan Hu2015-05-291-1/+10
| | | | | Closes https://github.com/gitlabhq/gitlabhq/issues/7105 See: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/130
* Change one-character variable namers-title-change-noteRobert Speicher2015-05-271-2/+2
| | | | [ci skip]
* Add a note when an Issue or Merge Request's title changesRobert Speicher2015-05-261-4/+21
|
* Updated rspec to rspec 3.x syntaxJeroen van Baarsen2015-02-121-11/+11
| | | | Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>
* Add labels notesNikita Verkhovin2015-02-081-1/+10
|
* Remove unnecessary reload in testDmitriy Zaporozhets2015-01-261-1/+1
|
* Organize event order execution when update issue or mrDmitriy Zaporozhets2015-01-251-1/+3
|
* Add action property to merge request hookjubianchi2015-01-201-4/+14
|
* Revert "Merge branch 'fix-email-threading' into 'master'"Jacob Vosmaer2014-06-181-1/+1
| | | | | | | | | This reverts commit 97fd990ecde387290be269ef7daafa5761f94af6, reversing changes made to f451a697e0c018359e6d8ff3aaba4eb0484c4bee. Conflicts: app/mailers/emails/notes.rb app/mailers/emails/projects.rb
* Send notification emails to the "project", and put people in CcPierre de La Morinerie2014-06-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes email threading in Mail.app, that doesn't like when a thread doesn't have stable recipients. For instance, here is a possible sender-recipient combinations before: From: A To: Me New issue From: B To: Me Reply on new issue From: A To: Me Another reply Mail.app doesn't see B as a participant to the original email thread, and decides to break the thread: it will group all messages from A together, and separately all messages from B. This commit makes the thread look like this: From: A To: gitlab/project Cc: Me New issue From: B To: gitlab/project Cc: Me Reply on new issue From: A To: gitlab/project Cc: Me Another reply Mail.app sees a common recipient, and group the thread correctly.
* Add note when MR assignee changes. Add more tests to MR servicesDmitriy Zaporozhets2014-04-031-0/+44
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
View Lorry Controller Status