-
Notifications
You must be signed in to change notification settings - Fork 11
Add documentation for establishing a SCM webhook and linking PRs. Also documentation for MCP-Auth #447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for pluraldocs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The key thing t highlight here is that it enables codebase root cause investigation in light of an alert or other issue. The example of this is in the boot-test environment's flow-test
flow, which is cross referencing against a pr
(also make sure the page is registered in the nav bar) |
…shing-a-scm-webhook-and-linking
…into john/prod-3468-add-documentation-for-establishing-a-scm-webhook-and-linking
description: Setting up SCM webhooks and automatically linking Pull Requests to Plural Flows | ||
--- | ||
|
||
# Overview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should explain this more, in particular:
- it will vector index the changes in the PR for future retrieval to find a code-derived root cause of an alert that might be firing
- it will appropriately link to the owning Flow to ensure the investigation is bounded by the permission structure you've already established within Plural, ensuring our AI is appropriately governed according to your requirements.
No description provided.