- 27 5月, 2015 1 次提交
-
-
由 Robert Speicher 提交于
Now there is a single source of information for which attribute a model uses to be referenced, and its special character.
-
- 30 4月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 17 4月, 2015 1 次提交
-
-
由 Robert Speicher 提交于
-
- 13 2月, 2015 1 次提交
-
-
由 Jeroen van Baarsen 提交于
Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
-
- 23 1月, 2015 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 06 10月, 2014 1 次提交
-
-
由 Vinnie Okada 提交于
Add tests for the new task list functionality in the Markdown parser and in issues and merge requests.
-
- 25 8月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 6月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 13 6月, 2014 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 28 5月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 4月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 23 1月, 2014 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 15 12月, 2013 1 次提交
-
-
由 skv 提交于
-
- 12 12月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 07 11月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 08 10月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 01 10月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 26 8月, 2013 1 次提交
-
-
由 ash wilson 提交于
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.
-
- 21 8月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 18 7月, 2013 2 次提交
-
-
由 Izaak Alpert 提交于
-Made the api method a little more readable -removed some missed extra newline's Change-Id: Ic38baafc813aaeda0a8b283f39916182c8ec37d5
-
由 Izaak Alpert 提交于
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
-
- 19 6月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 05 5月, 2013 1 次提交
-
-
由 Andrey Kumanyaev 提交于
-
- 15 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 20 2月, 2013 1 次提交
-
-
由 Andrew8xx8 提交于
-
- 18 2月, 2013 3 次提交
-
-
由 Andrew8xx8 提交于
-
由 Andrew8xx8 提交于
-
由 Andrew8xx8 提交于
-
- 05 1月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 03 1月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 19 12月, 2012 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 20 11月, 2012 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 13 11月, 2012 1 次提交
-
-
由 Vincent Bonmalais 提交于
-
- 07 11月, 2012 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 11 10月, 2012 1 次提交
-
-
由 Robb Kidd 提交于
* 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.
-
- 10 10月, 2012 1 次提交
-
-
由 Riyad Preukschas 提交于
-
- 09 10月, 2012 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 27 9月, 2012 1 次提交
-
-
由 Nihad Abbasov 提交于
-
- 08 9月, 2012 1 次提交
-
-
由 Riyad Preukschas 提交于
-
- 03 9月, 2012 1 次提交
-
-
由 Sytse Sijbrandij 提交于
Merge branch 'master' into non-interactive-aws-install Conflicts: doc/installation.md Fix merge mess in installation.md
-