Skip to content

Add the @security secalert command that enables team members to send emails to SecAlert directly from GitHub issue comments#63

Merged
stianst merged 1 commit into
keycloak:mainfrom
abstractj:secalert-new-mail
Mar 16, 2026
Merged

Add the @security secalert command that enables team members to send emails to SecAlert directly from GitHub issue comments#63
stianst merged 1 commit into
keycloak:mainfrom
abstractj:secalert-new-mail

Conversation

@abstractj
Copy link
Copy Markdown
Contributor

The command supports two flows:

  • New thread: @security secalert sends a new email and posts the thread ID back to the issue for future tracking.
  • Reply: when a SecAlert-Thread-ID already exists on the issue, subsequent invocations reply on the existing email thread regardless of subject.

@abstractj abstractj requested a review from stianst March 9, 2026 20:09
@abstractj abstractj force-pushed the secalert-new-mail branch 2 times, most recently from ecc5251 to 8d08159 Compare March 9, 2026 20:59
…emails

to SecAlert directly from GitHub issue comments

The command supports two flows:
- New thread: @security secalert <subject> sends a new email and posts the
thread ID back to the issue for future tracking.
- Reply: when a SecAlert-Thread-ID already exists on the issue, subsequent
invocations reply on the existing email thread regardless of subject.

Signed-off-by: Bruno Oliveira da Silva <bruno@abstractj.com>
@stianst stianst merged commit 294058c into keycloak:main Mar 16, 2026
2 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