Support Ops firmly believes that we should dogfood everything. In this belief, we utilize GitLab itself to handle updating many aspects of Zendesk. Through the use of GitLab, we:
To create a new object (macro, trigger, form, etc.) via the repo, you would
want to use the styling from a different file in the same repo. You then modify
the YAML coding in the file, leaving the id
value blank (as it doesn't exist
yet). If the object requires a position, you also want to leave that blank.
Once you are done editing, commit the changes to a new branch and generate a
merge request.
From there, the CI/CD scripts will run, comparing what is in the repo to what
is in Zendesk. It will then generate a report via the compare
job that
details what changes need to be made (how many creates, how many updates, etc.).
From there, you have two options:
id
and position
).To update an object via the repo, you simply edit the corresponding YAML file in the repo to use the desired changes. Once done, commit the changes to a new branch and generate a merge request.
From there, the CI/CD scripts will run, comparing what is in the repo to what
is in Zendesk. It will then generate a report via the compare
job that
details what changes need to be made (how many creates, how many updates, etc.).
From there, you have two options:
Reach out to the Support Operations Manager! They will also be willing to walk you through using the sync repos!