Make our internal CI runners report their status to github
Open
Nobody has claimed this yet.
good issue for AI
Testing
- Dominant language
- C++
- Stars
- 39
- Forks
- 22
- Avg merge
- 10h 22m
- Merged PRs (30d)
- 3
Description
Similar to Artemis
https://github.com/lanl/artemis/blob/develop/tst/launch_ci_runner.py
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
Read the referenced Artemis implementation in tst/launch_ci_runner.py first to understand how its CI runners report status to GitHub. Then locate the corresponding internal CI runner setup in singularity-eos and determine how to connect the same status reporting; done means the runners visibly report their status to GitHub.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100