wehub-resource-sync
b4fbd6fe9f
Deploy Site / deploy-vercel (push) Has been skipped
Deploy Site / deploy-docs (push) Has been skipped
Build Skills Index / build-index (push) Has been skipped
CI / Deny unrelated histories (push) Has been skipped
CI / Detect affected areas (push) Successful in 27m35s
CI / OSV scan (push) Failing after 4s
CI / Build&Test Docker image (push) Successful in 9s
CI / Supply-chain scan (push) Has been skipped
CI / Lint Docker scripts (push) Failing after 5m13s
CI / Check contributors (push) Failing after 12m8s
CI / Docs Site (push) Failing after 12m8s
CI / TypeScript (push) Failing after 12m8s
CI / Python lints (push) Failing after 12m9s
CI / Python tests (push) Failing after 12m9s
CI / Check uv.lock (push) Failing after 23m22s
CI / CI timing report (push) Has been cancelled
Build Skills Index / trigger-deploy (push) Has been cancelled
CI / All required checks pass (push) Has been cancelled
3.0 KiB
3.0 KiB
What does this PR do?
Related Issue
Fixes #
Type of Change
- 🐛 Bug fix (non-breaking change that fixes an issue)
- ✨ New feature (non-breaking change that adds functionality)
- 🔒 Security fix
- 📝 Documentation update
- ✅ Tests (adding or improving test coverage)
- ♻️ Refactor (no behavior change)
- 🎯 New skill (bundled or hub)
Changes Made
How to Test
Checklist
Code
- I've read the Contributing Guide
- My commit messages follow Conventional Commits (
fix(scope):,feat(scope):, etc.) - I searched for existing PRs to make sure this isn't a duplicate
- My PR contains only changes related to this fix/feature (no unrelated commits)
- I've run
pytest tests/ -qand all tests pass - I've added tests for my changes (required for bug fixes, strongly encouraged for features)
- I've tested on my platform:
Documentation & Housekeeping
- I've updated relevant documentation (README,
docs/, docstrings) — or N/A - I've updated
cli-config.yaml.exampleif I added/changed config keys — or N/A - I've updated
CONTRIBUTING.mdorAGENTS.mdif I changed architecture or workflows — or N/A - I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
- I've updated tool descriptions/schemas if I changed tool behavior — or N/A
For New Skills
- This skill is broadly useful to most users (if bundled) — see Contributing Guide
- SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
- No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
- I've tested the skill end-to-end:
hermes --toolsets skills -q "Use the X skill to do Y"