GitHub Issues integration

[brynary]

Integrate with GitHub Issues to create workflow runs from issues, update issue status based on run progress, and post run results as comments. Enable workflows that automatically pick up and work on labeled issues.

[jkfnc]

Also send plan as comment to Github Issue after its created with tag Plan and once tagged is removed after back and forth for a good plan, Start implementing ?

[fkukuck]

Hey @brynary ~ I'm working on the following proposal and wanted to discuss with you if this proposal for GitHub Issues intake resonates with your vision.

Proposal: GitHub Issue Intake for Fabro Workflows

Fabro workflows are usually started from the CLI or API. This workflow starts somewhere else: a GitHub issue.

This proposal adds a small convention for starting Fabro workflows from labeled GitHub issues. The mechanism is based on GitHub webhooks, but the workflow author only needs to configure labels and consume normal Fabro inputs.

What It Enables

A repository can define normal workflows such as:

• fix-bug
• implement-feature
• update-docs
• triage-issue

Maintainers can then start the right workflow by labeling an issue. For example:

• Add Bug and fabro to start fix-bug
• Add Feature and fabro to start implement-feature

Fabro comments on the issue when it starts the run, so contributors can follow what happened.

Repository Configuration

The repository adds one routing file on the default branch:

# .fabro/workflows/github.toml

[issues]
trigger_label = "fabro"

[[issues.workflow_labels]]
label = "Bug"
workflow = "fix-bug"

[[issues.workflow_labels]]
label = "Feature"
workflow = "implement-feature"

When the trigger label is added, Fabro checks the issue's current labels. Exactly one workflow label must match. If no workflow label matches, or multiple workflow labels match, Fabro comments on the issue and does not start a run.

Workflow names are simple names under .fabro/workflows/<name>/. They are not paths.

Workflow Inputs

The started workflow receives the issue as normal Fabro inputs:

Input	Description
github_issue_url	Issue URL
github_issue_number	Issue number
github_issue_title	Issue title
github_issue_body	Issue body, or an empty string
github_issue_author	Issue author login
github_repository	Repository, such as owner/repo
github_default_branch	Repository default branch
github_trigger_label	Trigger label, such as fabro
github_delivery_id	GitHub webhook delivery ID

Workflow authors use these exactly like any other input:

// .fabro/workflows/fix-bug/workflow.fabro

digraph FixBug {
    graph [goal="Fix GitHub issue: {{ inputs.github_issue_title }}"]

    start [shape=Mdiamond]
    fix [
        shape=box,
        prompt="Read {{ inputs.github_issue_url }} and fix the bug.\n\nIssue body:\n{{ inputs.github_issue_body }}"
    ]
    exit [shape=Msquare]

    start -> fix -> exit
}

Maintainer Flow

1. Create or update a GitHub issue.
2. Add one workflow label, such as Bug.
3. Add the trigger label, such as fabro.
4. Fabro starts the mapped workflow and comments on the issue.

To run the workflow again for the same issue, remove and re-add the trigger label.

Why This Shape

This keeps the workflow definition in the repository, next to the workflows it starts. Maintainers control routing with labels, and workflow authors get issue data through the same input mechanism they already use elsewhere in Fabro.