lhumina_code/hero_archipelagos
21
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions

Research and design event system for bot triggers #41

New issue
Open
opened 2026-03-25 13:53:35 +00:00 by timur · 0 comments
timur commented 2026-03-25 13:53:35 +00:00
Owner
Copy link

Context

Per hero_archipelagos#40, bots need to listen to events and automatically trigger workflow execution. No event infrastructure currently exists.

Research Needed

  • What event sources should be supported? (Forgejo webhooks, internal hero service events, external APIs, cron/scheduled)
  • What pub/sub or event bus architecture fits the hero ecosystem?
  • How do events map to bot workflow triggers?
  • Should events be processed by hero_proc (as scheduled actions) or a dedicated event router?

Possible Event Sources

  • Forgejo webhooks (commits, PRs, issues, releases)
  • Hero service lifecycle events (via hero_proc)
  • HTTP webhook receiver (generic external events)
  • Scheduled/cron triggers
  • Manual triggers (UI button)

Deliverable

A design document proposing the event architecture, data model, and integration points.

References

  • Parent issue: #40
## Context Per hero_archipelagos#40, bots need to listen to events and automatically trigger workflow execution. No event infrastructure currently exists. ## Research Needed - What event sources should be supported? (Forgejo webhooks, internal hero service events, external APIs, cron/scheduled) - What pub/sub or event bus architecture fits the hero ecosystem? - How do events map to bot workflow triggers? - Should events be processed by hero_proc (as scheduled actions) or a dedicated event router? ## Possible Event Sources - Forgejo webhooks (commits, PRs, issues, releases) - Hero service lifecycle events (via hero_proc) - HTTP webhook receiver (generic external events) - Scheduled/cron triggers - Manual triggers (UI button) ## Deliverable A design document proposing the event architecture, data model, and integration points. ## References - Parent issue: #40
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
lhumina_code/hero_archipelagos#41
No description provided.