bobbylite / bobbylite/hermes-admin-dashboard

Add configuration UI for automated backlog PR pipelines

Open
#6 0 comments 0 reactions 0 assignees View on GitHub
enhancement priority: medium
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Description
Currently, the automated backlog PR pipeline (managed via a cron job) is configured via a specific Hermes skill and internal rules. We need to expose these configurations in the Hermes Admin Dashboard to allow for easier management without manual intervention in the skill files.

## Requirements
- **Configuration UI:** A section in the admin dashboard to view and edit the current cron task settings (schedule, deliver targets, etc.).
- **Rule Management:** Ability to view and edit the current Orchestrator rules (e.g., branch naming conventions, priority rankings, and attribution settings).
- **Status Overview:** A dashboard view of the current pipeline status, including:
- Last successful run time.
- Current open PRs handled by the pipeline.
- Logs of recent actions (skipped, completed, failed).
- **Manual Trigger:** A button to manually trigger the 'hermes-dashboard-development' cron job immediately.

## Proposed Implementation
- Create a new configuration schema for the pipeline.
- Build a management page in the dashboard that allows users to update these parameters.
- Integrate with the Hermes Agent's configuration system to ensure the UI updates actually modify the active skills/cronjobs.

## Context
This is a direct follow-up to the need for making the automated coding workflows more transparent and editable by non-technical users.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue requires building a new UI section in the Hermes Admin Dashboard. Start by exploring the existing dashboard structure to understand how configuration pages are built and integrated. Look for the Hermes Agent's configuration system and the current cron job skill files to understand the data schema. The work involves creating a new configuration schema, a management page, and integrating with the backend to update active skills/cronjobs. 'Done' means the UI allows viewing/editing cron settings and rules, shows a status overview, and includes a manual trigger button.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design, devtools, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.