Slack Integration for Repo Updates

This guide wires GitHub Actions results to a Slack channel.

Option 1 (Fastest): Incoming Webhook + Workflow

Use this with .github/workflows/slack-notify.yml.

1) Create a Slack incoming webhook

1. Go to https://api.slack.com/apps and create/select your Slack app.
2. Enable Incoming Webhooks.
3. Add a new webhook to the target channel.
4. Copy the webhook URL.

2) Add GitHub repository secret

In GitHub repository settings:

1. Go to Settings -> Secrets and variables -> Actions.
2. Create secret: - Name: SLACK_WEBHOOK_URL - Value: webhook URL from Slack

3) Trigger and verify

• Open/update a PR to trigger the CI workflow.
• When CI completes, Slack Notify posts status + run URL to Slack.
• If SLACK_WEBHOOK_URL is missing, notification is skipped safely and the workflow step summary shows the status path.

Slack-style status path used by CI

• .github/workflows/ci-pr.yml posts a concise PR comment with:
• readiness gate status
• short status summary
• run URL
• Slack workflow path pointer
• .github/workflows/slack-notify.yml mirrors status + run URL and only sends channel messages when SLACK_WEBHOOK_URL exists.
• Failure triage guide: docs/CI_HEALTH_GATE_RUNBOOK.md.

Option 2: GitHub Slack App (No custom workflow required)

1. Install the GitHub app from Slack App Directory.
2. In your Slack channel, run: - /github subscribe raxx-app/TradeMasterAPI
3. Enable the events you want (PRs, issues, deployments, etc.).

This is simpler, but message format is less customizable than webhook + workflow.

Notes

• Incoming webhook posts to one channel unless you configure multiple webhooks.
• Keep webhook URL secret; rotate immediately if exposed.
• You can combine both options: GitHub app for broad events, webhook for CI-specific summaries.