missing build
Open
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
11:37 < [Coke]> c: 8bb460f2a e.say
11:37 < committable6> [Coke], ¦8bb460f: «Cannot test this commit (Commit exists, but an executable could not be built
for it)»
Contributor guide
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 examining commit 8bb460f2a and the committable6 message showing that no executable could be built for it. Trace how whateverable handles this build result and determine what behavior should occur when the commit exists but its executable is missing; done means the missing-build case is handled consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100