feat(eve): add @github-tools/eve-extension mountable eve extension#48
Merged
Conversation
Adds a real, supported eve extension distribution for the GitHub tools on top of the existing @github-tools/sdk/eve subpath, plus an examples/eve-extension-agent starter and docs.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Member
Author
|
@vercel review and add eve to the scope pr title |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
…`feat(eve): ...` titles fail semantic-pull-request validation with "Unknown scope 'eve'". This commit fixes the issue reported at .github/workflows/semantic-pull-request.yml:21 ## Bug In `.github/workflows/semantic-pull-request.yml`, the `amannn/action-semantic-pull-request` step restricts allowed conventional-commit scopes to: ```yaml scopes: | sdk chat deps ``` When `scopes` is set, the action enforces that any scope present in a PR title must be in the list. A PR title such as `feat(eve): add @github-tools/eve-extension ...` uses the `eve` scope, which is not in the list, so the action fails with: ``` Unknown scope 'eve' found in pull request title ``` This blocks the PR title validation check. ## Fix Added `eve` to the `scopes` list, preserving the existing pipe-multiline block and two-space indentation: ```yaml scopes: | sdk chat eve deps ``` Note: the PR title itself must still use the `eve` scope on GitHub — this config change only makes that scope valid. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com> Co-authored-by: HugoRCD <hugo.richard@vercel.com>
Member
Author
|
@vercel It must be said that in the future, it is the Eve mode expansion version that will be kept |
Both @github-tools/sdk/eve (direct import) and @github-tools/eve-extension (mountable eve extension) are supported today, but the extension is the direction this integration is moving toward and will become the recommended way to add GitHub tools to an eve agent.
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.
Summary
Adds
@github-tools/eve-extension, a mountable eve extension distribution for the GitHub tools, alongside the existing@github-tools/sdk/evesubpath (which remains the direct-import option).packages/github-tools-eve-extension— new package exposing a dynamic tool set (defineDynamic+buildEveToolMap) and an extension config schema (defineExtension) coveringtoken,connector(Vercel Connect),preset,requireApproval,overrides, and authoring fields (author,committer,coAuthors). Mounted tools are auto-namespaced by eve (e.g.github__listPullRequests).examples/eve-extension-agent— starter agent that mounts the extension via Vercel Connect, mirroringexamples/eve-agent's code-review setup.apps/docs/content/docs/2.frameworks/1.eve.mddocumenting the extension as an alternative to the direct@github-tools/sdk/eveimport.package.jsonscriptdev:eve-extension-agentto run the example from the repo root.@github-tools/sdk) documenting the new option.Verification
pnpm --filter @github-tools/eve-extension buildandtypecheckpass.eve build/eve infosucceed for the example agent with the extension mounted via the same Vercel Connect connector used byexamples/eve-agent.