docs: Document notification customization via Long-Term Context#315
Open
promptless[bot] wants to merge 4 commits intomainfrom
Open
docs: Document notification customization via Long-Term Context#315promptless[bot] wants to merge 4 commits intomainfrom
promptless[bot] wants to merge 4 commits intomainfrom
Conversation
Introduces a new page explaining how customers can customize Promptless notification behavior by editing doc_workflow/notification_skill.md in their organization's Long-Term Context. Covers notification defaults, templates, tone, delivery preferences, and Slack-specific features.
Reflects the button label change introduced in Promptless PR #2681. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…e": "CommitterType.USER", "files_deleted": [], "files_updated": ["src/lib/generated/sidebar.json"]}
| @@ -0,0 +1,70 @@ | |||
| --- | |||
Contributor
Author
There was a problem hiding this comment.
PR #2611 introduced customer-editable notification customization via Long-Term Context. Customers can customize notification defaults, templates, tone, and delivery preferences by editing doc_workflow/notification_skill.md in their organization's LTC.
| - **Channel support**: Receive notifications in specific channels by name, not just by ID | ||
|
|
||
| <Tip> | ||
| Promptless automatically detects protected branches in your documentation repository. When detected, Slack notifications show "Create PR" or "View PR" buttons instead of "Publish" to prevent merge errors. |
Contributor
Author
There was a problem hiding this comment.
PR #2681 changed the button label from "Open PR" to "Create PR"
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open this suggestion in Promptless to view citations and reasoning process
Adds a new documentation page explaining how customers can customize Promptless notification behavior.
What's new:
PR #2611 introduced customer-editable notification customization via Long-Term Context (LTC). Customers can now customize notification defaults, templates, tone, and delivery preferences by editing
doc_workflow/notification_skill.mdin their organization's LTC.Changes:
/docs/configuring-promptless/customizing-notificationsexplaining:doc_workflow/notification_skill.md)Revision (Mar 20): Updated button label from "Open PR" to "Create PR" to reflect the change in PR #2681, which replaced raw Slack Block Kit JSON with a fixed button enum.
Why this matters:
This is a new user-facing feature that was previously undocumented. Customers now have the ability to customize how Promptless notifies them about documentation suggestions, but without documentation they wouldn't know this capability exists or how to use it.
Related triggers: