- 25 Mar, 2014 14 commits
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Use humanize instead of titleize for MR title suggestion
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Proper message for archived projects at MR#show page Fixes #940
-
Dmitriy Zaporozhets authored
Print Styles
-
Dmitriy Zaporozhets authored
Sidekiq Load Check
-
Dmitriy Zaporozhets authored
External Issue Tracker Instructions
-
Dmitriy Zaporozhets authored
Inform people about the verify-none for webhooks. Fixes #980
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Fix the merge notification email not being sent
-
George Dewar authored
-
- 24 Mar, 2014 26 commits
-
-
Dmitriy Zaporozhets authored
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.
-
Dmitriy Zaporozhets authored
Applications js to coffee
-
Dmitriy Zaporozhets authored
Remove assignee/milestone selects from MR form Fixes #1079 and http://feedback.gitlab.com/forums/176466-general/suggestions/5663897-merge-request-assign-to-should-popule-with-membe
-
Jacob Vosmaer authored
Attribution For Shell Guide
-
Sytse Sijbrandij authored
Advise In Upgrade Guide Is Outdated
-
dosire authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Pierre de La Morinerie authored
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
-
Dmitriy Zaporozhets authored
Add gzip compression for assets to nginx example
-
Dmitriy Zaporozhets authored
-
Marin Jankovski authored
-
Sytse Sijbrandij authored
Update user_management.md
-
Dmitriy Zaporozhets authored
Show emoji in autocomplete when assets gzip compression is on
-
dosire authored
-
dosire authored
-
Marin Jankovski authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Robert Speicher authored
Removes the following from test output: DEPRECATION WARNING: It looks like you are eager loading table(s) (one of: merge_requests, projects) that are referenced in a string SQL snippet. For example: Post.includes(:comments).where("comments.title = 'foo'") Currently, Active Record recognizes the table in the string, and knows to JOIN the comments table to the query, rather than loading comments in a separate query. However, doing this without writing a full-blown SQL parser is inherently flawed. Since we don't want to write an SQL parser, we are removing this functionality. From now on, you must explicitly tell Active Record when you are referencing a table from a string: Post.includes(:comments).where("comments.title = 'foo'").references(:comments) If you don't rely on implicit join references you can disable the feature entirely by setting `config.active_record.disable_implicit_join_references = true`.
-
Dmitriy Zaporozhets authored
Small changes
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Conflicts: doc/release/monthly.md
-
Dmitriy Zaporozhets authored
Suppress 'Rendered...' log messages
-
dosire authored
-
dosire authored
-