Guides How-to

Make CI failures visible — and make recovery visible too.

Keep failing checks, jobs, and recoveries attached to the pull or merge request conversation instead of scattering alerts across chat.

Start free Read docs

How it works

Four steps from connection to a useful conversation.

1
Create or update a review route for the repository and turn on pull or merge request pipeline status.
2
For GitHub, accept the Checks and Actions permissions so ForgeRelay receives check and workflow changes.
3
For GitLab, enable both Pipeline and Job events so parallel job updates are visible instead of collapsed into one summary.
4
Choose whether pipeline updates stay in the request thread or post as a new channel message when a failure needs wider attention.

FAQ

Yes. Recovery is posted after a previous failure so the team can see that the request is ready to move again.

Yes. GitHub check events and GitLab Job events let ForgeRelay keep per-job detail in the message card.

No. They can update the existing pull or merge request conversation, preserving the context for reviewers.

Keep learning

Route GitHub pull requests to a Discord channel, open one public thread per request, and keep reviews and checks together.

Watch GitLab projects, open one Discord thread per MR, and keep pipeline failure and recovery beside the request.

Keep going

Free for up to three mapped people. Unlimited repos and notifications.

Start free