Skip to content

fix: honor --tags and --concurrency in baseline and compare - #51

Merged
royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
sharadvc:cursor/fix-baseline-compare-tags-465c
Sep 12, 2026
Merged

royalpinto007 merged 1 commit into
AgentPostmortem:mainfrom
sharadvc:cursor/fix-baseline-compare-tags-465c

Conversation

@sharadvc

Copy link
Copy Markdown
Contributor

Summary

cmdBaseline and the suite path in cmdCompare now use the same runOptionsFrom() helper as cmdRun, so --tags and --concurrency are applied consistently.

Test plan

  • npm test

Fixes #5

Factor shared runSuite options into runOptionsFrom and use it from
cmdRun, cmdBaseline, and cmdCompare so tag filters and concurrency match.

Fixes #5
@royalpinto007
royalpinto007 merged commit 8df1ff3 into AgentPostmortem:main Sep 12, 2026
9 checks passed
@github-actions

Copy link
Copy Markdown

This is in, @sharadvc. Really appreciate it.

Evalgate gets better every time someone outside the repo digs in like this.

If you find Evalgate useful, consider dropping a star. It helps more people find it.

Happy to see more from you whenever you have the time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--tags and --concurrency are ignored by baseline and compare

2 participants