semaphoreio / semaphoreio/semaphore

Webhook notifications for tags

Open
#369 0 comments 0 reactions 1 assignee View on GitHub

@hamir-suspect is already working on this.

Since Aug 19, 2025.

enhancement
Dominant language
Elixir
Stars
1.6k
Forks
89
Avg merge
1d 11h
Merged PRs (30d)
46

Description

Is your improvement proposal related to a problem? Please describe.

Users are trying to set up webhook notifications specifically for failed tag builds, but these notifications are not triggering as expected. Currently, webhook notifications in the YAML configuration don't support tag-based filtering, making it impossible to create notifications that trigger exclusively for tag builds. This is particularly problematic for users who use tags for production releases and need immediate alerts when tag builds fail.

Describe the solution you'd like

Add support for tag-based filtering in the YAML notification configuration:

notifications:
  - name: "Production Release Failures"
    type: webhook
    endpoint: "https://example.com/webhook"
    events:
      - pipeline_done
    filter:
      result: failed
      tag: "v*"  # New: filter by tag pattern
      
  - name: "Tag Build Notifications"
    type: webhook  
    endpoint: "https://example.com/webhook"
    events:
      - pipeline_done
    filter:
      result: failed
      ref_type: tag  # New: filter by reference type (tag vs branch)
      tag: "release-*"  # New: tag pattern matching

Key features needed:

  • ref_type field to distinguish between tag and branch builds
  • tag field for pattern matching on tag names
  • Ability to exclude branch builds when only tag notifications are desired
  • Support for wildcards and regex patterns in tag matching
Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.