Fastpath: Guide Admin > Customize design icon > Theme options menu > Update from GitHub
If you've set up the GitHub integration for your Guide theme, you manage your theme in GitHub and update the theme in Guide as needed.
You must be a Guide admin to update a GitHub-managed theme in Guide.
To update your Guide theme from GitHub
- In GitHub, make any changes to your theme, then increment the theme version number in the manifest.json file when you are ready to update the theme in Guide.
- In Guide, click the Customize design icon () in the sidebar.
The Themes page opens.
- Choose the GitHub-managed theme you want to update.
Any GitHub-managed theme has the GitHub logo beside the name of the theme.
- Click the options menu (), then select Update from GitHub.
- In Update from GitHub, click Update.
If you want to overwrite your theme settings in the Settings panel, deselect Keep theme settings. Otherwise the import will keep the theme settings as they are set in Guide and not overwrite them from GitHub.
Your theme updates in the Themes page.
I found this "Important: If you set up an integration with GitHub, making any modifications to your theme in Guide will break the GitHub integration." on https://support.zendesk.com/hc/en-us/articles/4408838187802-Working-on-a-theme-locally
How can I reverse the lost link with github?
Miguel Romero, once you've broken the link with GitHub, there is no way to restore it. Instead, you must pull another instance of your theme from GitHub and make it the live theme.
On the occasion that I need to break the GitHub integration in order to do some live testing, here is my process:
Thanks a lot, @David Bjorgen. I followed your process and it worked for me. I have to be very careful in the future when I edit. I appreciate your comments.
Is there a way to automate this action?
You can automate theme updates using GitHub actions and our Themes API.
When i try to update my file with github I have this message :
The version number of the imported theme is not allowed. Please contact the theme developer to verify that the version is compliant with the Semantic Versioning 2.0.0 standard and higher than the current version.
Somebody ever had the same problem ? what can i do ?
Hey Responsable-produit! That error indicate's the theme's version number in the manifest.json file does not comply with the versioning convention. This will need to be updated following convention.
Please sign in to leave a comment.