Xavier Morel 37cf6accb7 [FIX] forwardport: FP PR getting CI'd after initial FP check ... Test is probably more complex than necessary (thinking about it, the failed staging is probably unnecessary) but that triggers the issue and matches the original scenario. The problem was really with new CI events being received on the last forward-port PR of a sequence: previous PRs would have a child PR so the check would abort, but for the last PR it would go through, fail to find an active batch, then blow up as it tries to create a forwardport.batch without an actual batch. Change this to use the existence of an inactive batch not linked to a staging as a flag that the PR has been processed and forward-ported. Closes #218		2019-10-01 20:51:31 +02:00
..
__init__.py	[ADD] forwardbot	2019-09-05 10:00:07 +02:00
forwardport.py	[ADD] forwardbot	2019-09-05 10:00:07 +02:00
project.py	[FIX] forwardport: FP PR getting CI'd after initial FP check	2019-10-01 20:51:31 +02:00