This repository was archived by the owner on Nov 10, 2025. It is now read-only.
fix: Correct workflow name for run_unit_evals #1
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
This PR fixes a duplicate workflow name issue in GitHub Actions where the
run_unit_evals.ymlworkflow was incorrectly namedrun_agent_evals.Problem
The
.github/workflows/run_unit_evals.ymlfile had its workflow name set torun_agent_evalsinstead ofrun_unit_evals. This occurred because both workflow generation functions usednamed::workflow()which derives the name from the module name, causing both workflows to get the same name.Solution
tooling/xtask/src/tasks/workflows/run_agent_evals.rsto explicitly set the workflow namecargo xtask workflowsrun_unit_evalsChanges
.github/workflows/run_unit_evals.yml: Updated workflow name fromrun_agent_evalstorun_unit_evalstooling/xtask/src/tasks/workflows/run_agent_evals.rs: Explicitly set workflow nameTesting
✅ All workflow names are now unique
✅ No compilation errors or warnings
✅ YAML structure validated
This fix has also been submitted upstream to zed-industries/zed as PR zed-industries#42047.