Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
What changed
agent/connections/linear.tsusing Eve's MCP connection support and Vercel Connect.linear/veeauth for the shared V1 workspace.Why
Eve supports Linear through its remote MCP server at
https://mcp.linear.app/mcp. This wires the connector into Vee without storing Linear credentials in the repository.Verification
@vercel/connectdependency.Remaining setup
A Vercel Connect connector still needs to be created and attached to the Vee project using the UID
linear/vee, then the project must be deployed. The Linear workspace/team and the exact feature-request workflow should also be confirmed before enabling automatic ticket creation.