01 Apr, 2014
2 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
31 Mar, 2014
2 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
add 'Link' header for API response
26 Mar, 2014
5 commits
-
Add method to get the comments on a merge request
-
EventCreateService class The goal is to collect all event creation logic in one place called EventCreateService. Because now its placed in observers, controllers, services etc
-
Remove author_id_of_changes To prevent confusion because we already have `current_user`
25 Mar, 2014
8 commits
-
Update merge_request_observer_spec.rb
-
Remove Spork
-
added api method to return labels of a given project
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
24 Mar, 2014
4 commits
-
Don't send an email for "mentioned in" notes Currently, an email is sent every time a mentionable is referenced by an issue, a commit or a merge request: if I comment "This MR is related to #5", the watchers get one email for the comment, and another one stating "Issue #5 was mentioned by issue #13". This is annoying — but the biggest issue is when pushing an existing branch. Every issue referenced by commit messages in this branch will get a new mention (which is fine), and dozens of emails will be sent for all these new mentions (which is not). This commit fixes the spam by avoiding to send an email when a new mention is added to an existing mentionable. In most cases the email notification sent by the mentioner is enough.
-
The 'author_id_of_changes' attribute is not persisted in the database. As we retrieve the merge request from the DB just before sending the email, this attribute was always nil. Also there was no tests for the merge notification code - tests have been added. Fix #6605
-
Small changes
22 Mar, 2014
3 commits
-
[ci skip]
-
ping @karlhungus
21 Mar, 2014
1 commit
20 Mar, 2014
1 commit
-
Currently this method responds with `text/html`. It is kind of unusable if you open it in a browser. The browser thinks it is HTML and renders it as HTML, meaning new lines are dropped. So it's very hard to distinguish where the key starts and where it ends. This commit changes the content type header to `text/plain`.
19 Mar, 2014
6 commits
-
Add method to get the comments for a merge request and document that you can change the status of a merge request.
-
Speed up features/notes_on_merge_requests_spec
-
Uses the :simple merge request factory trait introduced by d166e70; cuts execution time of this spec in half.
-
This spec featured the slowest tests in the entire suite. After some debugging, the cause was found to be the large commit diff generated by comparing the stable and master branches. To fix this, the seed repository was modified to create a simple branch off of master that consists of three simple commits and minor changes. The spec was then updated to compare master to this branch instead of stable. The result is a spec group that runs in under 30 seconds, down from about 90.
18 Mar, 2014
1 commit
17 Mar, 2014
4 commits
-
Relative links within one system When using relative links in md in repository file it will only link within the repository. When using relative links in md in wiki page, it will only link to wiki pages.
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
16 Mar, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Conflicts: CHANGELOG
14 Mar, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
13 Mar, 2014
1 commit
-
Removes the "Removing gitlabhq" messages cluttering spec output