Timothy

Our helpdesk was recently setup with HSTS on help.example.com. Now I can no longer use ZAT theme preview for my theme preview. I keep getting these messages for all assets served over ZAT theme preview:

```

Mixed Content: The page at '' was loaded over HTTPS, but requested an insecure element ''. This request was automatically upgraded to HTTPS, For more information see
new:1 Mixed Content: The page at 'https://mysite.zendesk.com/hc/en-us/requests/new' was loaded over HTTPS, but requested an insecure element 'http://localhost:4567/guide/settings/logo.svg'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

```

How do I fix this?

Erica Girges is there any practical reason why we should do this? Does the ticket comment API not allow multiple file tokens to be attached to the same ticket comment?

It turns out that Zendesk Guide doesn't allow YAML files to be used in assets, but they show correctly when in local preview mode.

ZAT local preview mode should have the same behaviour when it comes to asset limiting.

Please add support for YAML assets. We use it for custom requests messages as it's more readable than JSON, but it's currently being blocked.

Eric Nelson so how does Zendesk manage to hide the manual zip-file uploading step from the user when they press "Update from GitHub"? Shouldn't the API also be able to bypass this step?

Hi Eric Nelson, I've read the link but it doesn't tell me how to trigger the Update from GitHub action available in the Theme settings page.

Hi Eric Nelson, yes that is the idea. I am trying to create a pipeline (on GitHub Actions) that would automatically increment the version and make Zendesk update the theme to the latest version.

Is there an API for instructing Zendesk to update a GitHub-linked Guide Theme from GitHub?

Whenever I start `zat theme preview`, ruby eats up 100% of my CPU. Can this be fixed?

Currently nesty input is a black box that's very hard for theme makers to inspect and modify. It should be made easier to modify them, possibly by including its CSS in Copenhagen or open-sourcing the component altogether.