iSEE/iSEEu

Disable merge requirements

Closed this issue · 1 comments

LTLA commented

Either disable merge requirements or pull iSEE from the GitHub master, otherwise the development cycle is too long if we have to wait for new API points to become available in iSEE.

Administrators can now "force merge" even when requirements fail.

That said, I think the checks should be kept running anyway, as I expect this 'development cycle' issue to be less of an issue after the early stages of iSEEu developments identify the relevant iSEE API updates.