You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
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?
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.
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.
Activity
J0WI commentedon Oct 21, 2018
Actually the checks run in background, but the API to expose the results is somehow broken.
Hainish commentedon Oct 22, 2018
@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 commentedon Oct 23, 2018
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 commentedon Oct 23, 2018
@Hainish did you already found something about the Travis issue?
Hainish commentedon Oct 23, 2018
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.