# Does anyone know why this repo's CompatHelper doesn't start CI?
**URL:** https://discourse.julialang.org/t/does-anyone-know-why-this-repos-compathelper-doesnt-start-ci/55061
**Category:** General Usage
**Tags:** github-actions
**Created:** [February 11, 2021, 2:21pm UTC](https://discourse.julialang.org/t/does-anyone-know-why-this-repos-compathelper-doesnt-start-ci/55061 "2021-02-11T14:21:35Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@BridgeBot](https://discourse.julialang.org/u/BridgeBot)
#### Post date: [February 11, 2021, 2:21pm UTC](https://discourse.julialang.org/t/does-anyone-know-why-this-repos-compathelper-doesnt-start-ci/55061/1 "2021-02-11T14:21:35Z")
Does anyone know why this repo’s CompatHelper doesn’t start CI? [https://github.com/SciML/DiffEqBayes.jl/pull/200](https://github.com/SciML/DiffEqBayes.jl/pull/200)
Note that the original poster on Slack cannot see your response here on Discourse. Consider _transcribing the appropriate answer back to Slack_, or pinging the poster here on Discourse so they can _follow this thread_.
[(Original message :slack:)](https://julialang.slack.com/archives/C6A044SQH/p1613053283050900?thread_ts=1613053283.050900&cid=C6A044SQH) [(More Info)](https://github.com/JuliaCommunity/SlackBridge)
---
### Author:  [@giordano](https://discourse.julialang.org/u/giordano)
#### Post date: [February 11, 2021, 4:19pm UTC](https://discourse.julialang.org/t/does-anyone-know-why-this-repos-compathelper-doesnt-start-ci/55061/2 "2021-02-11T16:19:41Z")
The reason why the pull request opened by CompatHelper didn’t trigger the continuous integration (CI) job is because in GitHub Actions, by default a workflow (CompatHelper in this case) can’t trigger another workflow (CI in this case). One workaround is to use the most recent recommended setup for CompatHelper (check out the [`README.md`](https://github.com/JuliaRegistries/CompatHelper.jl/blob/master/README.md)) which will use the SSH key `DOCUMENTER_KEY` to be able to trigger the CI job, provided that you have the key as a secret in your repository settings. Another, manual, workaround is to close and reopen the pull request: in this way the actor of the workflow will be you, not a GitHub Actions workflow, and so that would trigger CI as usual.