Adding a loose state (status_tag) to merge requests, adding state change to comments.
authorMarius Mathiesen <marius.mathiesen@gmail.com>
Fri, 12 Jun 2009 08:21:14 +0000 (10:21 +0200)
committerMarius Mathiesen <marius.mathiesen@gmail.com>
Wed, 24 Jun 2009 10:20:33 +0000 (12:20 +0200)
commitd4a271ef7971d79ff3a1d6b4380c028915db2bd6
treea4f5995cc51b1bcd91f8d105508457b038c3f6ba
parent84efb5b6e280634f04492cd85b88f385f6bda79d
Adding a loose state (status_tag) to merge requests, adding state change to comments.
- Adding a comment to a merge request now potentially sets or changes the loose state
of the merge request (target)

This way, target repository owners can mark that a merge request  should change state
when adding comments. This will eventually replace the more final reason from merge requests,
replacing it with comments with an added context
app/controllers/comments_controller.rb
app/models/comment.rb
app/models/merge_request.rb
app/views/comments/_comment.html.erb
app/views/comments/_form.html.erb
db/migrate/20090611124949_adding_state_change_to_comments.rb [new file with mode: 0644]
db/migrate/20090611125528_adding_status_tag_to_merge_requests.rb [new file with mode: 0644]
test/unit/comment_test.rb
test/unit/merge_request_test.rb