Https-everywhere: Travis CI not triggered by PRs

[J0WI]

Type: other

Travis CI is no longer triggered by PRs.

@Hainish could you have a look please?

[J0WI]

Actually the checks run in background, but the API to expose the results is somehow broken.

[Hainish]

@J0WI I'll take a look at this tomorrow.

I've noticed a lot of new issues for sites that don't yet have rulesets. Are you finding these issues useful, or should I encourage users who are automating these issue creations to stop?

[J0WI]

If the issue creation is automated it's not very helpful. Or is the bot open source, so that we can see the criteria (might be interesting to also auto generate rulesets)?
For manual created issues we know at least, that someone noticed that the site actually works over HTTPS.

[J0WI]

@Hainish did you already found something about the Travis issue?

[Hainish]

I've switched Travis from being a project service to GitHub app, and re-enabled the integration on the Travis CI side. It looks like it's working now, but I think you'll have to close and re-open PRs in order to initiate the CI in existing PRs.