Merge lp:~abentley/launchpad/more-diff-update-msg into lp:launchpad
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 12129 | ||||
Proposed branch: | lp:~abentley/launchpad/more-diff-update-msg | ||||
Merge into: | lp:launchpad | ||||
Diff against target: |
35 lines (+13/-1) 2 files modified
lib/lp/code/browser/branchmergeproposal.py (+3/-1) lib/lp/code/browser/tests/test_branchmergeproposal.py (+10/-0) |
||||
To merge this branch: | bzr merge lp:~abentley/launchpad/more-diff-update-msg | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tim Penhey (community) | Approve | ||
Review via email: mp+44288@code.launchpad.net |
Commit message
[r=thumper]
Description of the change
= Summary =
Fix bug #525698: MP diff update message should be shown before scanning
== Proposed fix ==
Show the same message when the source branch needs scanning as when the diff is
being updated.
== Pre-implementation notes ==
None
== Implementation details ==
I simply updated the pending_diff property on the view.
Since the source branch is only considered to need scanning if the revision id
has changed, it is very likely that the diff will need an update if
pending_diff is true.
== Tests ==
bin/test -t test_pending_
== Demo and Q/A ==
Create a merge proposal. Commit a new revision and push to the source branch
immediately. The merge proposal should immediately show that the diff is being
updated.
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/