Rename split-CI trigger labels to `run ci github-runner` and `run ci kkt-runner`
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Domain
- ci-cd, documentation
Research direction
Open WORKFLOWS.md and locate the split-CI trigger label references for github-runner and kkt-runner. Rename them to run ci github-runner and run ci kkt-runner, then review the document to confirm the old labels are no longer presented as triggers.
Written by the indexing model from the issue text.
Description
In WORKFLOWS.md, instead of github-runner and kkt-runner I would prefer run ci github-runner and run ci kkt-runner.
The run prefix signals that the label triggers an action, and ci indicates what is being triggered.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 6
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.
More from control-toolbox/Handbook
-
Integration tests Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Local reg and betas Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in control-toolbox/Handbook
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100