Often a repository will pass CI on the main repo, but fail on the master of a forks.
This can be because
the fork build didnt have required tokens added, or
the build logic only works on the main repo
the build on the main repo only works because of its cache
coala has repos in all these situations frequently enough that we need to detect this.
The tool can get a list of all forks, find the most recent builds that pass and fail, and guess whether a new fork build will pass or fail.
The analysis wont be perfect, but if it erroneously reports that a fork build might fail, the reaction will be for someone to do a new build on a fork, which should result in the tools analysis to become correct.
Often a repository will pass CI on the main repo, but fail on the
master
of a forks.This can be because
coala has repos in all these situations frequently enough that we need to detect this.
The tool can get a list of all forks, find the most recent builds that pass and fail, and guess whether a new fork build will pass or fail.
The analysis wont be perfect, but if it erroneously reports that a fork build might fail, the reaction will be for someone to do a new build on a fork, which should result in the tools analysis to become correct.
This is related to https://github.com/ksdme/org-status/issues/9