Hive is adding a gh-aw on-ramp, but I do not want to submit an untested runnable workflow to this gallery.
Proposed entry: a “Hive triage” agentic workflow that triggers from GitHub issues/PRs, invokes hive for deterministic filter/classify/admission checks, then returns results to GitHub as labels/comments and (when policy allows) dispatches to the configured coding-agent CLI. Hive would remain the neutral orchestration layer: GitHub/GitLab work sources, local/Kubernetes execution, and policy gates before agent work; gh-aw would be one trigger path, not a dependency.
I checked the repo and saw workflows/, docs/, and the import workflow that appears to import/adapt a working .md workflow and compile a lock file. I also saw some external community links in the README.
Concrete ask: what is the acceptance bar for adding a Hive-backed triage entry here, and do cross-platform orchestrators that include GitLab/local/Kubernetes targets fit the Agentics gallery scope?
Hive tracking issue: hivecommons/hive#10625
Hive is adding a gh-aw on-ramp, but I do not want to submit an untested runnable workflow to this gallery.
Proposed entry: a “Hive triage” agentic workflow that triggers from GitHub issues/PRs, invokes
hivefor deterministic filter/classify/admission checks, then returns results to GitHub as labels/comments and (when policy allows) dispatches to the configured coding-agent CLI. Hive would remain the neutral orchestration layer: GitHub/GitLab work sources, local/Kubernetes execution, and policy gates before agent work; gh-aw would be one trigger path, not a dependency.I checked the repo and saw
workflows/,docs/, and the import workflow that appears to import/adapt a working.mdworkflow and compile a lock file. I also saw some external community links in the README.Concrete ask: what is the acceptance bar for adding a Hive-backed triage entry here, and do cross-platform orchestrators that include GitLab/local/Kubernetes targets fit the Agentics gallery scope?
Hive tracking issue: hivecommons/hive#10625