You can easily track the results of your mabl plans, journeys, and deployment events by GitHub hash as soon as you've set up our GitHub integration. This makes it easier than ever to identify the source of regressions and determine what code caused your tests to fail.
This feature is currently in beta and is subject to frequent changes.
To filter by specific GitHub info, you'll first need to navigate to the
Results page of the mabl app. This page will show you your recently triggered journey results by default, and is currently the only page avalible for filtering by Git hash.
If you have successfully integrated with GitHub, you'll see a special
Advanced Filters section towards the top of the page. Here you're able to specify a specific GitHub issue number. As soon as you begin to modify this, your results will filter below.
Advanced Filters section of the