Timmy_Foundation/timmy-config
15
0
Fork 0
Code Issues 99 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

CI: Comprehensive config validation pipeline (YAML, Python, Shell, JSON, Cron, Playbooks) #431

Open
perplexity wants to merge 1 commits from perplexity/ci-validation-pipeline into main
pull from: perplexity/ci-validation-pipeline
merge into: Timmy_Foundation:main
Conversation 0 Commits 1 Files Changed 1 +134
perplexity commented 2026-04-09 01:14:42 +00:00
Member
Copy Link

Problem

The repo has zero CI validation (#289). Agents commit broken YAML, invalid JSON, Python syntax errors, and malformed cron entries with no automated detection. The only existing workflow is the PR checklist gate.

Solution

7 parallel CI jobs that run on every PR and push to main:

Job What it catches
yaml-lint Broken YAML configs across all playbooks and configs
json-validate Invalid JSON (agent-lanes.json, channel_directory.json)
python-check Syntax errors + critical flake8 (undefined vars, import errors)
shell-lint Shellcheck errors in deploy.sh and cron scripts
cron-validate Malformed cron entries
deploy-dry-run Broken deploy.sh syntax
playbook-schema Missing required keys in playbook YAML files

Impact

Prevents the #1 source of fleet frustration: broken configs reaching main and silently failing in production.

Ref: #289, #395

## Problem The repo has zero CI validation (#289). Agents commit broken YAML, invalid JSON, Python syntax errors, and malformed cron entries with no automated detection. The only existing workflow is the PR checklist gate. ## Solution 7 parallel CI jobs that run on every PR and push to main: | Job | What it catches | |-----|----------------| | yaml-lint | Broken YAML configs across all playbooks and configs | | json-validate | Invalid JSON (agent-lanes.json, channel_directory.json) | | python-check | Syntax errors + critical flake8 (undefined vars, import errors) | | shell-lint | Shellcheck errors in deploy.sh and cron scripts | | cron-validate | Malformed cron entries | | deploy-dry-run | Broken deploy.sh syntax | | playbook-schema | Missing required keys in playbook YAML files | ## Impact Prevents the #1 source of fleet frustration: broken configs reaching main and silently failing in production. Ref: #289, #395
perplexity added 1 commit 2026-04-09 01:14:45 +00:00
ci: add comprehensive config validation workflow
Some checks failed
PR Checklist / pr-checklist (pull_request) Failing after 4m6s
Details
6336525232
perplexity requested review from Timmy 2026-04-09 01:14:45 +00:00
Some checks failed
PR Checklist / pr-checklist (pull_request) Failing after 4m6s
Details
This pull request doesn't have enough required approvals yet. 0 of 1 official approvals granted.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin perplexity/ci-validation-pipeline:perplexity/ci-validation-pipeline
git checkout perplexity/ci-validation-pipeline
Sign in to join this conversation.
Reviewers
No Reviewers
Timmy
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#431
Delete Branch "perplexity/ci-validation-pipeline"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?