Use the mabl GitHub integration to generate GitHub issues based on mabl insights that are important to your team, such as test plan failures, page load issues, or significant changes in test run time.
If you want to take an action other than making a GitHub issue for a mabl insight, see the article on Generating custom GitHub events for more powerful integration options.
Setup
To get started, follow the instructions outlined in the GitHub integration setup article.
When you reach the GitHub integration page in mabl, toggle on the following settings:
- "Create GitHub RepositoryDispatch events for mabl insights"
- "Create GitHub issues for mabl insights"
Use the toggles and dropdowns in the Filter insights section to filter the insights that are important to your team. See the setup guide for a complete list of insight filters.
Filtering insights
Run tests
To generate GitHub issues from mabl insights, configure your CI/CD workflow to trigger a mabl deployment event and associate the deployment event with the GitHub code revision hash.
When a deployment occurs, mabl traces plan runs that start as part of the deployment event back to the source repository using the code revision hash. In the event that a failure insight occurs, such as when a previously passing plan run starts to fail, the insight is automatically filed as a GitHub issue with the respective details.
A sample GitHub issue created from a mabl insight
Managing GitHub issue creation
See the GitHub integration setup article for full details on customizing this feature's behavior.
.