Xavier Morel ef24adad88 [FIX] runbot_merge: cancel button on staging ... * split action_cancel (UI button) from cancel (internal): since the xhr mapping is weird, if there are available args the mapper thinks it should pass the call context as reason which is unexpected * make cancel a no-op when called on already inactive stagings * make cancel work when called on multiple statgings * make computing the active staging work properly in an active_test=False context (e.g. when it's interacted with from the form view because that comes from the list view which is active_test=False, probably so we can see not just the stagings but recursively see deactivated batches in deactivated stagings) * don't show the cancel button on inactive stagings		2019-08-27 12:28:53 +02:00
..
__init__.py	[ADD] runbot_merge: a merge bot	2018-09-03 13:16:36 +02:00
pull_requests.py	[FIX] runbot_merge: cancel button on staging	2019-08-27 12:28:53 +02:00
res_partner.py	[IMP] runbot_merge: don't quote signoff	2019-03-04 13:17:10 +01:00