Explain which eval failed
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 322
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Around here:
Rework the message to somehow include what failed to eval. I'm thinking something like:
- nix-env failed to evaluate the ${branch} mainline branch
- nix-env failed to evaluate with the PR changes
Additionally, maybe a grey result instead of a ❌ on failure to eval the mainline branch? Though I'm thinking it may be risky "no ❌ so it must be fine to merge".
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 at ofborg/src/nixenv.rs lines 149-154 and trace where evaluation failures are turned into result messages. Distinguish failures evaluating the ${branch} mainline from failures evaluating PR changes, then verify that both messages identify the failed evaluation and that any status change still communicates failure clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100