- 10 Oct, 2013 3 commits
-
-
Izaak Alpert authored
Change-Id: I05e02ff7e36e2350cdf5d2b94095ada9760a204e
-
Izaak Alpert authored
Change-Id: I1ffe18414b7f6eae38d7860a8e3b64a9a185273f
-
Izaak Alpert authored
Change-Id: Ia50c3ac043b4c927ca59cbbdc2bba42f73e550e4
-
- 12 Sep, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Trigger notification service when new user-group relation was created
-
- 25 Aug, 2013 1 commit
-
-
ash wilson authored
Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown references in descriptions, titles, or attached Notes creates a back-reference Note that links to the original referencer. Furthermore, pushing commits with commit messages that match a (configurable) regexp to a project's default branch will close any issues mentioned by GFM in the matched closing phrase. If accepting a merge request would close any Issues in this way, a banner is appended to the merge request's main panel to indicate this.
-
- 14 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Jul, 2013 3 commits
-
-
Izaak Alpert authored
-Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
-
Izaak Alpert authored
-Disable observers post test run -Allow db:seed_fu RAILS_ENV=test to be run more than once without error -fix diffs_in_between, was passing in the default_options for grit, but grit in this case doesn't take options, fixed the test to actually fail if the incorrect diffs are returned -make notes/commits render against proper project -MR discussion file links should reference note's project -Added tests for commit links on edit merge request -fixes edit issues (canceling an edited mr, updating an edited mr) -updates tests with checks for source code updates -still forked_merge_requests.feature (project_forked_merge_requests) test not passing (commented out -- "stable" not being set) MR API: error on bad target_project -If the target project id is specified and it is not the same as the project the request is being made on (the source), and the it isn't a fork of that project, error out, otherwise use it as the target -Fixes some busted (but hidden) test cases Conflicts: app/views/merge_requests/show/_diffs.html.haml spec/features/notes_on_merge_requests_spec.rb Change-Id: I20e595c156d0e8a63048baaead7be6330c738a05
-
Izaak Alpert authored
The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
-
- 25 Jun, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 May, 2013 1 commit
-
-
Andrey Kumanyaev authored
-
- 01 May, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 10 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 Mar, 2013 3 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 20 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Feb, 2013 2 commits
-
-
Andrew8xx8 authored
-
Andrew8xx8 authored
-
- 13 Feb, 2013 1 commit
-
-
Andrew8xx8 authored
-
- 11 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 28 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 15 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 09 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 02 Jan, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 21 Dec, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 14 Dec, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 23 Nov, 2012 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 13 Nov, 2012 1 commit
-
-
Vincent Bonmalais authored
-
- 17 Oct, 2012 1 commit
-
-
Riyad Preukschas authored
-
- 13 Oct, 2012 1 commit
-
-
Robb Kidd authored
The fact that Notes on Walls have a noteable_type value of "nil" got lost in the refactoring of the observer.
-
- 11 Oct, 2012 1 commit
-
-
Robb Kidd authored
-
- 10 Oct, 2012 1 commit
-
-
Robb Kidd authored
* Move is_assigned? and is_being_xx? methods to IssueCommonality This is behavior merge requests have in common with issues. Moved methods to IssueCommonality role. Put specs directly into merge_request_spec because setup differs for issues and MRs specifically in the "closed" factory to use. * Add MergeRequestObserver. Parallels IssueObserver in almost every way. Ripe for refactoring. * Rename MailerObserver to NoteObserver With merge request observing moved out of MailerObserver, all that was left was Note logic. Renamed to NoteObserver, added tests and updated application config for new observer names. Refactored NoteObserver to use the note's author and not rely on current_user. * Set current_user for MergeRequestObserver IssueObserver and MergeRequestObserver are the only observers that need a reference to the current_user that they cannot look up on the objects they are observing.
-
- 26 Sep, 2012 1 commit
-
-
Alex Denisov authored
-
- 19 Sep, 2012 1 commit
-
-
Gabor Liptak authored
-