Try to formalize the "concern" syntax for MCPs #709
Merged
Conversation
This file contains 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
|
r? @BoxyUwU (rustbot has picked a reviewer for you, use r? to override) |
rustbot
added
the
S-waiting-on-review
|
@Mark-Simulacrum gentle nudge. thanks. |
Mark-Simulacrum
approved these changes
Dec 7, 2023
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.
Sibling PR to rust-lang/triagebot#1747
Context: I'm trying to encourage a homogenous syntax to raise and resolve concerns in MCPs, so it'll be easier to parse the github comments and summarize the consensus status of the MCP.
As mentioned in the other PR, the suggested syntax mimics the FCP but will not activate anything nor will emit errors. It's just formalizing a syntax.
Rendered
cc: @Mark-Simulacrum for a 👍