submodules for benchmarks
Open
enhancement
second-order enhancement
- Dominant language
- Shell
- Stars
- 19
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In the future when we have more time, we should use git submodules for the benchmarks so we're not duplicating code.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating the benchmark code and identifying what is duplicated, then determine the intended submodule source and update workflow. Done requires an agreed design and a clear benchmark integration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100