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
Hi!
I configured my project to report the quality of the docs after the builds of Travis, but it seems something is broken with Inch CI due I still see the "how-to" configure Inch CI for an Elixir project in the master branch (if I select the HEAD branch I see the reports).
For the GitHub sync issue I get an mixed content error due the mix of protocols. The error is:
Mixed Content: The page at 'https://inch-ci.org/github/ivanhercaz' was loaded over HTTPS, but requested an insecure script 'http://inch-ci.org/sync_projects?_=1589202465389'.
This request has been blocked; the content must be served over HTTPS.
It seems there is some opened issues reporting this (#211, #245, #183) and one PR (#212) in which @matoakley proposes a solution. I decided to open a new issue due I am also reporting something that I think it may be a side-effect, or not (the situation I mentioned in the first paragraph).
Thank you for this project, @rrrene. It is very interesting and useful.
The text was updated successfully, but these errors were encountered:
Hi!
I configured my project to report the quality of the docs after the builds of Travis, but it seems something is broken with Inch CI due I still see the "how-to" configure Inch CI for an Elixir project in the master branch (if I select the HEAD branch I see the reports).
For the GitHub sync issue I get an mixed content error due the mix of protocols. The error is:
It seems there is some opened issues reporting this (#211, #245, #183) and one PR (#212) in which @matoakley proposes a solution. I decided to open a new issue due I am also reporting something that I think it may be a side-effect, or not (the situation I mentioned in the first paragraph).
Thank you for this project, @rrrene. It is very interesting and useful.
The text was updated successfully, but these errors were encountered: