Update Github CI status indicator when invoking `@ofborg eval`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Sometimes eval fail due to a socket error or something, and posting @ofborg eval will fix it. The problem is that the CI badge remains a red X until the eval has been completed, which may take a few hours depending on the queue. This poor feedback has led to many instead opting to rebase-force-push the PR rather than invoke @ofborg eval, simply because they think @ofborg eval doesn't work. This in turn makes viewing the diff between force-pushes unviable.
It would be great if the CI status indicators immediately turn yellow when invoking @ofborg eval, like they already do for @ofborg build xyz
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 tracing how the @ofborg eval command updates CI status indicators, comparing it with the existing @ofborg build xyz behavior. Confirm the current status transition and identify the relevant tests or entry points; done means invoking @ofborg eval immediately changes the indicator to yellow before evaluation completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100