What is the GitHub integration for Guide themes?

Pinned

16 Comments

  • Vladan Jovic

    Hey Gorka, first of all, thank you and your team on hard work for making this happen!

    Until now, I have just one basic question:

    • I exported my theme to GitHub repo
    • pulled from the repo to my PC and imported the code into my IDE (Sublime text)
    • I made one change, eg font color: red;
    • Can I see my change locally before commit?
      If not, is that on the road in the coming times?

    Thanks and happy holidays! 
    Vlad 

    0
  • Allen Hancock

    Hi Vlad!

    Zendesk's ZAT toolset provides a way to view changes locally, though plan restrictions may apply.

    Hope this helps!

    -Allen

    0
  • Vladan Jovic

    Thanks, Allen! I totally forgot about this tool! :)

    1
  • Gorka Cardona-Lauridsen

    Perfect! Jep ZAT should solve it :)

    @Allen, Thanks for answering!

    @Vlad, Apologies for my late reply due to holidays and thanks for the appreciation of the teams work!

    1
  • Anthony Kotenko

    This is awesome!

    We have a number of instances of Zendesk, each with its own theme, in our case. Would it be possible to upload to them from different branches in a single repository? So, not to create the repository for each one. 

    0
  • Gorka Cardona-Lauridsen

    Thanks Anthony!

    In the current incarnation of the feature it is not possible to designate which branch to fetch from, we always fetch the default branch, but as we are in a feedback gathering phase it is not ruled out as a functionality to include :)

    To understand your use case, could you tell me more about why you prefer hosting each theme as different branches in the the same repo as opposed to a repo for each theme and how your workflow is around that?

    0
  • Anthony Kotenko

    @Gorka Thank you for the answer, the feature is very important for us, since in our current case we have around 15 instances on production and so 15 on staging as well, together it's 30 — and it's would be hard to maintain such a large number of repositories. 

    0
  • Gorka Cardona-Lauridsen

    🎉 Update from Github is now available in the EAP! 🎉

     

    2
  • Gorka Cardona-Lauridsen

    🎁Now you can choose which branch you want to fetch from! 🌵

    3
  • Anthony Kotenko

    Wow, that feature is just awesome and really helps a ton! Thank you!

    1
  • Thomas Berger

    Sounds great! We are using GitLab, will this be supported?

    0
  • Scott Currie

    Will this also work with git repos in Microsoft Azure Dev Ops (Visual Studio Online)? If it is only for GitHub, we won't be able to use the feature.

    Looks like the only potential issue would be the authorization for private repos.

    0
  • Maria McDowell

    This is such a great feature I can't believe I didn't see it until today. Thank you for the little pop-up asking me to try it. We have been using github for the theme since we started, and this saves the step of zipping the theme and uploading.

    I have a workflow question: We typically use a modified gitflow workflow, which in this case means that we would test the develop branch or PRs on our sandbox or using ZAT Theme Preview. We would then tag a release, and that would run on prod.

    So, Is it possible to select a TAG rather than a branch (not crucial, we can always merge into a production branch)?

    In addition, I would really like to be able to implement something like the following:

    1. Make changes locally, testing via ZAT theme preview
    2. Push to a test/develop branch on github.
    3. Allow a tester (agent) to log onto Guide, select the develop branch of the theme FOR THIS INSTANCE ONLY and test. I.e., rather than have testers have to run ZAT theme preview, I would like them to be able to test themes on live content without affecting the actual public/prod appearance.

    Currently, the only way to allow non-developers to test and review is put the theme on our Sandbox, but that does not contain all our current content. I realize this isn't really a git-specific request, but we use git heavily and allowing better testing on alternative branches would be enormously helpful. I don't want every tester to have to implement our entire repo/zat as that slows our process down and all they are really doing is providing UI feedback.

    0
  • Gorka Cardona-Lauridsen

    Hi Maria

    Thank you for the thorough feedback!

    Unfortunately it is currently not possible import based on a tag, but it is great feedback and I will take it up with the team. I have to be honest and say that it will not be in the first release of the feature as we are releasing soon, but we will continue to develop on the integration to allow for other workflows and use cases than we are currently addressing.

    Regarding your request to allow non-developer testers to select a dev branch for that instance only, we are investing a lot in enabling more complex development, testing and delivery workflows going forward, so it would be very interesting to understand your workflow better. I will send you an e-mail to see if we can setup a call.

    0
  • Elisabeth Wetchy

    Really great feature, thank you for making this happen!

    Would there be any issue with connecting themes for multiple Zendesk instances to the same Github repo? We have a sandbox instance as well as the live one, and I'd like to use the sandbox as a staging area to test changes before I pull them into the live instance.

    0
  • Gorka Cardona-Lauridsen

    Hi Elisabeth, thank you, glad you like the feature :)

    There should be no issue with connecting several Zendesk instances to the same GitHub repo or the same branch in the same repo. Sounds like for your workflow it would make sense to connect the sandbox to the development branch(es) and the live theme on the live instance to the master branch.

    If you wish to preview anything on your live content in your live instance, without making changes to the live theme, you can also either use ZAT (Zendesk app tools) or use the online preview of non-live themes.

    0

Post is closed for comments.

Powered by Zendesk