From 423eccf4d5eb28d9b9f874f00d494a6bbd225c6c Mon Sep 17 00:00:00 2001 From: Andreas Thomas Date: Wed, 23 Oct 2024 15:46:50 +0200 Subject: [PATCH] Add steps for using in a thread --- examples/github-pr-alerts-workflow/README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/examples/github-pr-alerts-workflow/README.md b/examples/github-pr-alerts-workflow/README.md index 93ffba2..056eefd 100644 --- a/examples/github-pr-alerts-workflow/README.md +++ b/examples/github-pr-alerts-workflow/README.md @@ -9,6 +9,15 @@ This workflow expects the following secrets to be set in the repository: - `CAMPSITE_API_KEY`: The API key for the Campsite API (we suggest creating a dedicated "GitHub" integration for this) - `CAMPSITE_PR_ALERTS_THREAD_ID`: The ID of the thread in Campsite where the PR alerts should be posted +#### Using a thread + +If you’re trying to send a message to a thread, you need to add the integration to the thread first: + +1. Open the thread in Campsite +2. Click the ••• menu in the top corner +3. Click “Manage integrations” +4. Add your integration to the thread + ### How we use it We use this workflow internally at Campsite to post messages in a thread whenever a pull request is opened, closed, or merged. We use an API key from a custom "GitHub" integration so messages are posted as if they came from GitHub.