Add MCP unresolved concerns to T-compiler meeting agenda #1759
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
Mark-Simulacrum
approved these changes
Jan 16, 2024
apiraino
force-pushed
the
add-mcp-concerns
branch
from
93aa914 to
6f6bc7b
Compare
apiraino
force-pushed
the
add-mcp-concerns
branch
from
6f6bc7b to
d0cb94a
Compare
|
rebased. gentle ping for merge @ehuss @Mark-Simulacrum 🙏 |
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.
Some more automation when generating the T-compiler meeting agenda: now adding the unresolved concerns to the team MCPs (to help having a quick overview during the meeting).
Discussed the idea during a meeting on Zulip.
The parsing of the MCP concerns is a bit brittle, I'm basically grepping through the comments looking for the markers we introduced in #1747 but I hope it's good enough for now
r? @ehuss @Mark-Simulacrum
Thanks!