JuliaCI / JuliaCI/BaseBenchmarkReports
Add a nested folder structure (instead of keeping everything at the root level)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The BaseBenchmarkReports repository has become very difficult to browse.
What do you think of adding some kind of structure, instead of storing all folders at the root level.
Maybe something like year/month/day/name_of_job?
@maleadt did something similar for the PkgEval reports and it was a great improvement: see https://github.com/maleadt/BasePkgEvalReports/issues/1 and https://github.com/maleadt/BasePkgEvalReports/commit/3b0254eefa19ac39979420b38d6b402ab241f13c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository root and the linked BasePkgEvalReports issue and commit for the prior report-organization example. Define the folder structure and migration scope with maintainers; the work is done when reports are organized consistently and existing report links or references remain usable.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100