Skip to main content
Connect the Factorize GitHub App in the browser and approve the selected repositories. Ask list_github_installations({}) for safe installation IDs. Select the repository in the browser job editor to obtain its numeric repository ID; MCP does not provide a repository picker. Append this trigger to a successful manual job, preserving the complete configuration:
Replace illustrative IDs with the selected installation/repository IDs. GitHub requires either non-empty issue match rules or both event and action. Read the saved trigger’s slug/reflection before using fields such as {{trigger-2.pull_request.number}}. Give the execution agent its own repository access. Open one test PR on the selected repository. Verify delivery timeline, job activity and run context, then output in the browser trace. Missing events often mean wrong repository selection, a suspended installation or event/action mismatch. Use event troubleshooting. Delayed conflict workflows also verify live PR state; conditions previews do not perform that verification.