thefederationinfo/github-integration

Github Integration Server

github-integration's Issues

Make repo entries update-able

In case someone wants to change configuration e.g. trigger flags introduced in here #8

Separate html stuff from go code

Add opt-in/out feature for ci tests

Also I don’t know if there should be something like [ci skip] for it, or maybe even the opposite, run only when there is [federation] or a federation-label at the PR (as a setting per repo if default on or off). Because there are also many frontend PRs which would only add unnecessary load to travis. And while I would have it enabled by default for the federation repos, I would have it default-off for the diaspora-repo (because most PRs there are not related to federation, only when updating the federation lib or some refactorings, it would be interesting to run the tests there too).

related to https://sechat.org/posts/3581013#45b550300a0e0136176b52540061b601

Displayed name of the testsuite in a pull request

Currently the server will show up as Federation Suite like in this example:

But all the current implementations like Travis, codedov and so on.. are using a format like this:
continuous-integration/travis-ci/pr

Shall we do the same? How should that look like?

continuous-integration/thefederation/pr

Allow a regex in opt-in/out flags

see #8 (comment)

Make builds update-able

We create a entire new build in the db if the sha differs (if not it fails)
its buggy if e.g. the PR was re-opened.