ci: add test workflow with automated cybersyn notification #4

Merged
brad merged 3 commits from ci/notify-cybersyn into main 2026-02-14 22:46:42 -08:00
Collaborator

Summary

Adds CI/CD workflows for automated testing and Cybersyn infrastructure notification.

Changes

  • test.yaml: Runs vitest tests on push to main and PRs

    • Uses node:20-bookworm container (standard for our infrastructure)
    • Runs npm ci for clean dependency installation
    • Executes npm test (vitest)
    • On success (main branch only), triggers notify-cybersyn workflow via workflow_dispatch
  • notify-cybersyn.yml: Updated to support workflow_dispatch

    • Can now be triggered manually or by the test workflow
    • Still triggers on push to main (existing behavior)
    • Notifies cybersyn infrastructure of 5e-tools-mcp updates

Testing

  • ✓ Both YAML files validated with Python YAML parser
  • ✓ Follows conventional commits
  • ✓ Follows existing workflow patterns from ~/commune/cybersyn

Notes

  • Test workflow only triggers cybersyn notification on main branch (not PRs)
  • Requires DISPATCH_TOKEN secret to be configured in repo settings
## Summary Adds CI/CD workflows for automated testing and Cybersyn infrastructure notification. ## Changes - **test.yaml**: Runs vitest tests on push to main and PRs - Uses `node:20-bookworm` container (standard for our infrastructure) - Runs `npm ci` for clean dependency installation - Executes `npm test` (vitest) - On success (main branch only), triggers notify-cybersyn workflow via workflow_dispatch - **notify-cybersyn.yml**: Updated to support workflow_dispatch - Can now be triggered manually or by the test workflow - Still triggers on push to main (existing behavior) - Notifies cybersyn infrastructure of 5e-tools-mcp updates ## Testing - ✓ Both YAML files validated with Python YAML parser - ✓ Follows conventional commits - ✓ Follows existing workflow patterns from ~/commune/cybersyn ## Notes - Test workflow only triggers cybersyn notification on main branch (not PRs) - Requires `DISPATCH_TOKEN` secret to be configured in repo settings
ci: add test workflow with automated cybersyn notification
Some checks failed
Test / test (pull_request) Has been cancelled
0f6dd7bc3f
- Add test.yaml workflow that runs on push to main and PRs
- Runs vitest tests with npm ci for clean dependency install
- Triggers notify-cybersyn workflow on successful test (main branch only)
- Update notify-cybersyn.yml to support workflow_dispatch for manual/automated triggering
- Uses node:20-bookworm container (standard for our infrastructure)
- Follows conventional commits and existing workflow patterns
ci: make test and notify-cybersyn workflows independent
All checks were successful
Test / test (push) Successful in 30s
Test / test (pull_request) Successful in 1m9s
c0dbcb672f
- Remove chained trigger from test.yaml to notify workflow
- Test now runs on all pushes and PRs (branch protection enforces)
- Notify runs independently only on main branch pushes
- Use 'npm install' instead of 'npm ci' in test workflow
- Update notify to trigger deploy-mcp.yaml (correct workflow name)
- Both use runs-on: docker with node:20-bookworm container

These workflows are independent - branch protection is the enforcement
mechanism that ensures tests pass before merging to main.
chore: resolve merge conflict with main (deploy-mcp.yaml is correct)
All checks were successful
Test / test (pull_request) Successful in 26s
Notify Cybersyn / notify (push) Successful in 3s
Test / test (push) Successful in 1m15s
54b368da5e
brad merged commit 54b368da5e into main 2026-02-14 22:46:42 -08:00
brad deleted branch ci/notify-cybersyn 2026-02-14 22:46:42 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dungeonchurch/5e-tools-mcp!4
No description provided.