Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The performance README points to a measure script at the wrong path

Open Beginner friendly
#1,446 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
shell
Domain
documentation

Research direction

Start with docs/benchmarks/performance/README.md:10 and the example at docs/benchmarks/performance/measure-cli.sh:7. From the repository root, run both documented --help commands and confirm they print the script usage; done means both examples resolve the existing script path and the documentation check passes.

Written by the indexing model from the issue text.

Description

area:build bug good first issue sev:papercut

Found on santos/dev2 at 008363c98 (#1410). On dev@debffabf6 too.

What happened

The documented command names docs/benchmarks/measure-cli.sh, which does not exist. The executable is docs/benchmarks/performance/measure-cli.sh. The same stale path is on dev.

Replication

Deterministic (no model). From a clean checkout, run the README's path with --help. The shell reports that the file does not exist. Run docs/benchmarks/performance/measure-cli.sh --help; it prints usage.

Where

docs/benchmarks/performance/README.md:10 contains the stale command. The script's own example at docs/benchmarks/performance/measure-cli.sh:7 also uses the stale path, at 008363c98.

The fix

Use the existing performance/measure-cli.sh path in both examples.

Acceptance

  • e2e: both documented --help commands execute from the repository root and print the script's usage.
  • Unit: a documentation check resolves every local script path in these examples.
  • The change entry's invalidates names the former path.
Dominant language
Go
Stars
115
Forks
14
Avg merge
9h 38m
Merged PRs (30d)
730

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Agent-Field/CodeAF

All issues in Agent-Field/CodeAF

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.