Repository navigation
docs: Document configuring triggers and context sources in the dashboard, not only in promptless.yaml - #1148
Open
promptless[bot] wants to merge 5 commits into
Open
promptless[bot] wants to merge 5 commits into
promptless[bot] wants to merge 5 commits into
Conversation
…as an alternative
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
…hboard-path # Conflicts: # src/content/docs/docs/for-docs/connect/triggers.mdx
…hboard-path # Conflicts: # src/content/docs/docs/for-docs/connect/context-sources.mdx # src/content/docs/docs/for-docs/connect/context-sources/confluence.mdx # src/content/docs/docs/for-docs/connect/context-sources/google-drive.mdx # src/content/docs/docs/for-docs/connect/context-sources/jira.mdx # src/content/docs/docs/for-docs/connect/context-sources/linear.mdx # src/content/docs/docs/for-docs/connect/context-sources/notion.mdx # src/content/docs/docs/for-docs/connect/doc-locations/github-repos.mdx # src/content/docs/docs/for-docs/connect/triggers.mdx # src/content/docs/docs/for-docs/connect/triggers/github-commits.mdx # src/content/docs/docs/for-docs/connect/triggers/github-prs.mdx # src/content/docs/docs/for-docs/connect/triggers/gitlab-merge-requests.mdx # src/content/docs/docs/for-docs/connect/triggers/jira.mdx # src/content/docs/docs/for-docs/connect/triggers/launchdarkly.mdx # src/content/docs/docs/for-docs/connect/triggers/slack-messages.mdx # src/content/docs/docs/for-docs/reference/integrations/atlassian.mdx # src/content/docs/docs/for-docs/start-here/open-source-quickstart.mdx # src/content/docs/docs/for-docs/tune/noise-and-relevance-filtering.mdx # src/content/docs/docs/for-docs/tune/notifications.mdx
Contributor
Author
|
I noticed that some CI checks failed for this PR. I'm investigating whether the failures are caused by this suggestion. If they're unrelated or pre-existing, I'll leave this suggestion unchanged and create a separate suggestion if a standalone docs fix is needed. |
This branch was successfully deployed
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.
Requested by: Frances Liu
Proposed changes
The trigger, context source, and doc collection pages described configuration as editing
promptless.yaml, even though the dashboard's Configuration page opens in a form editor that covers the same settings. This change leads each configuration section with the dashboard steps (exact labels from the Triggers, Context sources, Doc collections, and Policies tabs) and keeps the YAML as the alternative for YAML mode.updatedmode: removes the "Review-bot setup withupdated" subsection, which showed config for a "review bot" without explaining it. The page'supdatedmode section explains the behavior. The Configuration section keeps one example of addingupdatedto a clause and one for triggers that userepos: all. It also notes thatupdatedis set in YAML mode, because the dashboard's When should Promptless run? options don't include it.Checklist
Verification: labels checked against the dashboard source (
promptless-dashboard/src/app/configuration/structured/) and on the live Configuration page. After mergingmain(#1177), the first dashboard step on the trigger pages was split into two sentences to stay under the ValeDirect.Lengthlimit. Vale (src/content/docs, error level), remark lint, andmanni meta validatepass on the branch.