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

ref builders: failed git status is accepted as a clean source tree

Open Beginner friendly
  • Is something wrong?
#265 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Burntgogi is already working on this.

Since Oct 15, 2026.

  • #272 by @Burntgogi — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
git, shell
Domain
tooling

Research direction

The same check is in tools/ref/build-hidden.sh (around line 21), tools/ref/build-nemotron-ref.sh (around line 19) and tools/ref/clefvis/build-clefvis.sh (around line 31). Start by reading how each script tests the output of git status inside a command substitution, then reproduce by stubbing git status to exit 128. Done when all three scripts exit non-zero on that failure, with the status captured in a standalone assignment before its output is tested.

Written by the indexing model from the issue text.

Description

review-bot

The hidden, nemotron and clefvis builders put git status inside a test's command substitution. A corrupt or unreadable Git index makes status exit 128 with empty stdout. The test then treats the tree as clean. rev-parse HEAD does not need that index, so the scripts can compile unchecked headers and record the commit as their provenance. Validation reproduced exit 0 after a status stub returned 128; the standalone assignment exited 128. Capture git status in a standalone assignment before testing its output; set -e then stops on failure.

Evidence (at the base of #242):

Filed by Shingler, the review bot, while reviewing #242; the defect is outside that pull request.

Dominant language
Rust
Stars
21
Forks
4
Avg merge
3h 27m
Merged PRs (30d)
194

Getting set up

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 midagedev/bloomery

All issues in midagedev/bloomery

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.