DataStrategist / DataStrategist/notes2kg
CI lint gate never executes — no self-hosted runner registered for this org
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Problem
The `CI — Parse and Lint R` workflow (`.github/workflows/ci.yml`) — added 2026-08-04 as part of a cross-repo lint-drift audit — is correctly configured (full-repo scan, hard-fail on any lintr violation) but every recorded workflow run (checked back to 2026-03-06, 4 runs) shows `status: completed, conclusion: cancelled` after ~24h. That's GitHub Actions' default queue timeout for a `runs-on: self-hosted` job that no runner ever picks up.
Root cause
This repo lives under the `DataStrategist` GitHub org. The working self-hosted runner used successfully by other ASC repos (helplines_data, ascFuncs, signal_processing, admin, chatbot_content, chatbot_data, case_data/advicePro_queries, cc — all confirmed green CI) is registered under the `access-social-care` org, not `DataStrategist`. There's no runner available to claim jobs here.
Impact
Repo's 3 R files (`pos_maker.R`, `shiny.R`, `runner.R`) currently have 119 lint violations under default linters. The gate was added today specifically to catch this, but it has never actually executed against real code, so the drift remains uncaught regardless of the new config.
Fix options
- Register a self-hosted runner scoped to `DataStrategist` (or this repo specifically), matching the access-social-care setup, or
- Move this repo under the `access-social-care` org where the working runner is already registered, or
- Switch `runs-on: self-hosted` to a GitHub-hosted runner (`ubuntu-latest`) if self-hosted isn't actually required.
Same root cause as a parallel issue filed on `DataStrategist/monday-pipeline` — both repos are on the wrong org for the available runner. Not fixing in the lint-drift cleanup PR — this is a separate infra decision.
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 with .github/workflows/ci.yml and compare its self-hosted runner configuration with the working access-social-care repositories named in the issue. Confirm which runner or hosting arrangement the DataStrategist org supports, then verify that the CI — Parse and Lint R workflow is picked up and completes instead of timing out; the chosen infrastructure option must be explicit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, r
- Domain
- ci-cd, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100