No notification on conflicts in merge proposals
Bug #336439 reported by
Paul Hummer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When a branch is submitted for review, and it has conflicts, a notification should be emitted to (at least) the submitter. It would also be nicer if subscribers should also got an email about it.
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: code-review email |
| Changed in launchpad: | |
| importance: | Medium → Low |
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #1 |
Revision history for this message
| Drew Freiberger (afreiberger) wrote | #2 |
To post a comment you must log in.
and ideally each time either the branch is submitted it should notify if there are conflicts or not...