docs: Document commit trigger approaches and private channel access#222
docs: Document commit trigger approaches and private channel access#222promptless[bot] wants to merge 2 commits intomainfrom
Conversation
promptless
bot
requested review from
adit-chandra,
frances720,
mattlink and
prithvi2206
as code owners
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| 3. **Relevance Assessment**: Promptless determines if the changes require documentation updates | ||
| 4. **Suggestion Creation**: If relevant, Promptless creates documentation suggestions | ||
|
|
||
| ## Commit Triggers vs. Pull Request Triggers |
There was a problem hiding this comment.
Citation: Based on prithvi's explanation of the two approaches: (1) commits + PRs for getting PR comments plus updated suggestions after merge, or (2) commits only for teams who find PR triggers too noisy. When using commits only, you won't get PR comments so a Slack notification channel is recommended.
View source
| By default, Promptless only reads Slack content when you explicitly trigger it by tagging @Promptless or using the "Update Docs" message action. If you enable passive listening in your project settings, Promptless will monitor only the specific channels you select. Promptless cannot access private channels unless it has been specifically invited to those channels. | ||
| By default, Promptless only reads Slack content when you explicitly trigger it by tagging @Promptless or using the "Update Docs" message action. If you enable passive listening in your project settings, Promptless will monitor only the specific channels you select. | ||
|
|
||
| ### Adding Promptless to Private Channels |
There was a problem hiding this comment.
Citation: Based on prithvi's advice that if a notification channel is private, you need to add Promptless to it first—the easiest way is to tag @promptless in that channel.
View source
|
|
||
| 1. Go to your [project settings](https://app.gopromptless.ai/projects) | ||
| 2. Click the pencil icon to edit your GitHub Commits project | ||
| 3. Add your preferred Slack channel at the bottom of the project settings |
There was a problem hiding this comment.
Citation: PR #1898 changes the notification channel from a text input to a dropdown selector in EditProjectModal.tsx and NewProjectModal.tsx. Added note about refreshing channels on Integrations page based on PR description.
View source
Open this suggestion in Promptless to view citations and reasoning process
Documents two approaches for using GitHub commit triggers and explains how to configure Slack notification channels.
Changes to GitHub Commits trigger page:
Changes to Slack integration page:
@Promptlessin the channelTrigger Events
Internal discussion about verifying documentation coverage for customer questions and identifying which article sections to reference.
Promptless Research (1 Slack conversation)
Agent Response
Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)