A collection of MakerX reusable workflows and configs.
This repository uses Release Please to automate releases based on Conventional Commits.
When referencing workflows or actions from this repository, you can pin to specific versions using the following tag formats:
| Tag | Example | Description |
|---|---|---|
| Full version | v1.2.3 |
Pin to an exact release (recommended for production) |
| Minor version | v1.2 |
Automatically receive patch updates |
| Major version | v1 |
Automatically receive minor and patch updates |
| Latest | latest |
Always points to the most recent release |
# Pin to exact version (most stable)
uses: MakerXStudio/shared-config/.github/workflows/example.yml@v1.2.3
# Pin to minor version (receives patch updates)
uses: MakerXStudio/shared-config/.github/workflows/example.yml@v1.2
# Pin to major version (receives minor and patch updates)
uses: MakerXStudio/shared-config/.github/workflows/example.yml@v1
# Always use latest (not recommended for production)
uses: MakerXStudio/shared-config/.github/workflows/example.yml@latestWhen contributing to this repository, use Conventional Commits to ensure proper versioning:
feat: description- New feature (bumps minor version)fix: description- Bug fix (bumps patch version)feat!: descriptionorBREAKING CHANGE:in body - Breaking change (bumps major version)
Release Please will automatically create a release PR when changes are pushed to main. Merging this PR triggers the release.
For more information, see the Release Please documentation.
The zendesk github integration consist of 3 github actions.
- github_zendesk_issue_labelled.yml
- github_zendesk_issue_commented.yml
- github_zendesk_issue_closed.yml
Once an issue is assigned a specified label, it is sent to Zendesk,
creating (or using) the user <Github UserName> with email <Github UserName>@users.noreply.github.com.
This mail adress format is also used by github when a user sets the privacy option that the mail should be hidden.
Once the ticket got created a comment to the issue will be added to inform the user about the tech support contact.
Every comment on an issue gets send to zendesk. It will look up the connected ticket and author and attaches the comment to the ticket.
When an issue is closed, it is marked as solved in Zendesk.
The workflows need to be added to each repository that we want to sync issues to Zendesk. However, to avoid repeat code, they can also be reused via Calling a reusable workflow. Samples can be found here.
There are known limitation of GitHub - Zendesk integration:
- Markdown comments aren't supported due to an issue with Zendesk API.
- When an issue is created, existing comments aren't synced to Zendesk.
- Comment updates aren't synced to Zendesk.
- Removing issue label from GitHub doesn't have an affect, the corresponding Zendesk ticket is still need to be handled manually.
- The GitHub actions don't have retry logic, if they failed, the data won't be synced.
Zendesk - GitHub integration is done via webhook and Zendesk events. Zendesk events will trigger GitHub workflows of a GitHub repository (let's call it the entry point). From this entry point, it works out the target repository for dispatching workflows. Currently, there are:
You can find the Postman collection for Zendesk API here. Import the collection and the global variables to your local postman. There are some variables to set:
- zendesk-tenant-name: Zendesk tenant name (it also is called subdomain), can be found in the URL. For example, for https://my-subdomain.zendesk.com/, it's my-subdomain
- zendesk-auth-token: Zendesk auth token. See https://support.zendesk.com/hc/en-us/articles/115000510267-How-can-I-authenticate-API-requests-#heading2
- zendesk-webhook-id: Zendesk webhook Id, we will set that later
- github-owner: GitHub repository owner
- github-repo: The repository which Zendesk will trigger the workflow from
- github-pat: GitHub personal access token, it needs to have repository permission
contents:writeto the entry point repository
Steps:
- Run
Create webhookAPI to create the Zendesk webhook. Remember to take note of the responseidand set thezendesk-webhook-idvariable. - Run
Create trigger - ticket solvedAPI - Run
Create trigger - ticket commentedAPI
From GitHub side, there are:
They will be invoked by zendesk_github_ticket_commented and zendesk_github_ticket_solved respectively. They need to be added to each repository that we want to sync comments and statuses from Zendesk. However, to avoid repeat code, they can also be reused via Calling a reusable workflow. Samples can be found here.
Zendesk - GitHub integration needs GH_ZENDESK_INVOKE_WORKFLOW_TOKEN secrets to invoke the workflows. It's a personal access token, the only requirement is to have permission contents:write to any repository that we want to sync from Zendesk.