Goal: Automate the commit and push of GitHub ticket metadata (local .md files) to remove the burden of manual "Ticket Sync" commits from the human developer.
Context:
Currently, the github-workflow MCP server automatically runs sync_all on startup, updating the local .github/ISSUE/ files. However, the commit and push of these changes remains a manual task for the developer. Including these changes in feature commits pollutes the diffs. A GitHub Action is suboptimal due to potential git push conflicts.
Solution:
Implement a "Janitor" capability within the Neo Agent OS (Node.js runtime).
- Trigger: Periodic (e.g., every 30 mins) or Event-based (after Agent task completion).
- Action:
- Run
sync_all tool (to capture any mid-session updates).
- Check
git status for changes in .github/ISSUE/ or .github/RELEASE_NOTES/.
- If changes exist:
git add .github && git commit -m "chore: Ticket Sync [skip ci]" && git push.
- Constraint: Should verify the repo is clean/idle to avoid disrupting user work.
Why:
To automate metadata hygiene without polluting feature history or causing remote merge conflicts.
Goal: Automate the commit and push of GitHub ticket metadata (local
.mdfiles) to remove the burden of manual "Ticket Sync" commits from the human developer.Context: Currently, the
github-workflowMCP server automatically runssync_allon startup, updating the local.github/ISSUE/files. However, the commit and push of these changes remains a manual task for the developer. Including these changes in feature commits pollutes the diffs. A GitHub Action is suboptimal due to potentialgit pushconflicts.Solution: Implement a "Janitor" capability within the Neo Agent OS (Node.js runtime).
sync_alltool (to capture any mid-session updates).git statusfor changes in.github/ISSUE/or.github/RELEASE_NOTES/.git add .github && git commit -m "chore: Ticket Sync [skip ci]" && git push.Why: To automate metadata hygiene without polluting feature history or causing remote merge conflicts.