Robb Kidd 16ceae895e Separate observing of Note and MergeRequests ... * 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.		2012-10-10 17:59:25 -04:00
..
activity_observer_spec.rb	Move observer specs out of spec/models into spec/observers	2012-08-25 13:22:45 -04:00
issue_observer_spec.rb	Notification sends to issue author and assignee if issue being reopened or closed	2012-08-29 10:48:17 +03:00
key_observer_spec.rb	Use similar interface to access gitolite	2012-08-29 00:04:06 +03:00
merge_request_observer_spec.rb	Separate observing of Note and MergeRequests	2012-10-10 17:59:25 -04:00
note_observer_spec.rb	Separate observing of Note and MergeRequests	2012-10-10 17:59:25 -04:00
user_observer_spec.rb	Fix observer test	2012-09-12 09:05:12 +03:00
users_project_observer_spec.rb	Comment removed	2012-09-26 17:01:13 +03:00