Skip to content

Add reusable PR Slack notification workflow - #105

Merged
timkelty merged 3 commits into
v3from
timkelty/notify-craft-cloud-reviews
Aug 18, 2026
Merged

Add reusable PR Slack notification workflow#105
timkelty merged 3 commits into
v3from
timkelty/notify-craft-cloud-reviews

Conversation

@timkelty

@timkelty timkelty commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Description

Adds a reusable workflow that posts pull request details to a configured Slack webhook. Calling workflows decide which pull request events and conditions should trigger a notification.

Related issues

None.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds an org-level reusable GitHub Actions workflow to send a Slack notification when the craft-cloud team is requested as a pull request reviewer.

Changes:

  • Introduces a workflow_call-based workflow that posts a structured Slack message (via jq + curl) for Craft Cloud review requests.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/notify-craft-cloud-review.yml Outdated
Comment thread .github/workflows/pr-slack-notification.yml
@timkelty timkelty changed the title Notify Slack when Craft Cloud reviews are requested Add reusable PR Slack notification workflow Aug 18, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/pr-slack-notification.yml:25

  • This reusable workflow assumes it’s called from a PR-triggered workflow (it reads github.event.pull_request.*). If a caller invokes it from a non-PR event (e.g., workflow_dispatch/schedule), these expressions resolve empty and the workflow will still post a misleading Slack message with missing link/title/author. Consider validating the required PR fields at runtime (and fail fast with a clear error) to make the reusable interface safer.
        run: |
          set -o pipefail

@timkelty
timkelty merged commit 1481cac into v3 Aug 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants