- 03 Mar, 2014 3 commits
-
-
Pierre de La Morinerie authored
Emphasize the meaningful informations, and remove the less needed ones: * Use "!" to identify a merge request * Write the name of the commented file for diff notes * Don't show the assignee in the "merged merge request" email
-
Pierre de La Morinerie authored
* Less margin: the content appears as the text of the message. * Streamlined footer: everything on one line, with a small separator. * Zimbra (www.zimbra.com) chokes on HTML tables, and doesn't display the content of the message. Switching to a simpler layout fixes the issue.
-
Pierre de La Morinerie authored
Every email has a different way of showing a link to the discussion on the website. We don't need this anymore, as we now have a standard "View in GitLab" link in the footer of every email.
-
- 30 Aug, 2013 1 commit
-
-
James Newton authored
-
- 18 Jul, 2013 1 commit
-
-
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
-
- 12 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 31 Dec, 2012 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 10 Aug, 2012 1 commit
-
-
Robert Speicher authored
Didn't bother with files in db/, config/, or features/
-
- 06 Aug, 2012 1 commit
-
-
Riyad Preukschas authored
-
- 16 May, 2012 1 commit
-
-
Robb Kidd authored
Update method to take ids and then perform #finds itself during mailer queue worker kick-off.
-
- 23 Apr, 2012 1 commit
-
-
gitlabhq authored
-
- 13 Feb, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Dec, 2011 1 commit
-
-
Valery Sizov authored
-
- 15 Oct, 2011 2 commits
-
-
Dmitriy Zaporozhets authored
-
gitlabhq authored
-
- 13 Oct, 2011 2 commits
-
-
Dmitriy Zaporozhets authored
-
gitlabhq authored
-
- 08 Oct, 2011 1 commit
-
-
gitlabhq authored
-