docs: add executor to getting started manifest#435
Merged
Conversation
Co-authored-by: Copilot App <[email protected]> Copilot-Session: 0e61c749-26a1-4e90-94e7-cfa33d17e5ef
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the docs site’s Getting Started evaluation manifest so it includes an explicit executor setting, ensuring the example eval.yaml conforms to the expected schema and runs without requiring API access.
Changes:
- Add
config.executor: mockto the Getting Startedeval.yamlexample.
Show a summary per file
| File | Description |
|---|---|
site/src/content/docs/getting-started.mdx |
Adds executor: mock to the sample eval manifest under config so copied starter manifests are schema-valid. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Low
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
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
The Getting Started
eval.yamlexample omitted the requiredconfig.executorfield, so copied manifests did not conform to the schema. Addexecutor: mockto make the starter manifest valid without requiring API access.Related issue
Closes #436
Agent handoff
site/src/content/docs/getting-started.mdxmock, matching the repository's existing getting-started and example manifests.Type of change
Validation
go test ./...make lintorgolangci-lint runweb/changedconfig.executor.Documentation
site/docs updated, if CLI, YAML, dashboard, or validator behavior changedRisk and rollback
Notes for reviewers
No behavior changes; verify the starter manifest remains aligned with the eval schema.