PR adds a special behaviour to the logic for uploading coverage reports that can survive the outage and maintenance of the remote UI (e.g. was the case for coveralls). I am not sure if it would be better to make this behaviour configurable, but in our case, it resulted in failing our PR within CI. Let me know if it makes sense and/or suggestions for improvement.
Coverage increased (+0.2%) to 90.485% when pulling f8451775821160e374a3934b458ef2dfcda43d11 on tgrk:survive-coveralls-maintenance into a215645c028026ff24b42add6f8acabe91008abf on parroty:master.
PR adds a special behaviour to the logic for uploading coverage reports that can survive the outage and maintenance of the remote UI (e.g. was the case for coveralls). I am not sure if it would be better to make this behaviour configurable, but in our case, it resulted in failing our PR within CI. Let me know if it makes sense and/or suggestions for improvement.