Xavier Morel b8408546a0 [FIX] runbot_merge: stagings dashboard ... Mistake in the statuses handling: the context is not sufficient to uniquely identify a staging status as different repositories can get the same status context (e.g. ci/runbot is present on all our repositories). This is only a visual problem, but the status dropdown on stagings (both the dashboard and the branchwise listing) would reuse one of the status with the context for all of them, leading to incorrect links and misleading displays. Fix by keying on (repo, context) instead, that's exactly why the repository name was part of the status in the first place.		2020-07-29 08:42:56 +02:00
..
mergebot.xml	[ADD] runbot_merge: allow overriding statuses	2020-07-14 13:34:05 +02:00
res_partner.xml	[ADD] runbot_merge: allow overriding statuses	2020-07-14 13:34:05 +02:00
templates.xml	[FIX] runbot_merge: stagings dashboard	2020-07-29 08:42:56 +02:00