For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/integrations/github.md.
Docs
  • 26.11

    • GitHub integration

    The GitHub integration connects your repositories to Flezise so the builder agent can read source code, react to CI failures and pull request reviews, and open pull requests when work is done.

    The GitHub integration detail page showing Connected status, an Inbound events card with the Allow work-item triggers toggle on, and a Write-back card

    Connect

    Open Project Settings → Integrations → GitHub. Click Connect to authorize via OAuth, or Connect with token to enter a Personal Access Token directly.

    OAuth requests these scopes: repo, read:org, and workflow. The repo scope covers private repository access; workflow allows the integration to read and re-run GitHub Actions.

    Token connect accepts one credential field:

    FieldWhat to enter
    Personal Access TokenA classic or fine-grained token starting with ghp_

    Generate the token at GitHub → Settings → Developer settings → Personal access tokens. The token needs the repo and workflow scopes, plus admin:repo_hook so Flezise can register the events webhook for you.

    Flezise registers the webhook when you link a repository (see Configuration). To register it by hand instead, copy the Webhook URL from the connection panel and add it under the repository's Settings → Webhooks, with content type application/json and the Signing Secret from the same panel as the secret.

    Capabilities

    CapabilityWhat it means
    WebhooksReceives and verifies inbound events from GitHub
    ReplyPosts comments back to issues and pull requests
    Source PullProvides an authenticated clone URL for the linked repository
    PR CreateOpens a pull request via the GitHub API when a run completes

    Configuration

    After connecting, enter the repository in owner/name format in the Source control card on the detail page and press Link repository. This saves the repository and links it in one step. The builder agent then uses that repository for cloning and pull requests without requiring a separate choice for each run.

    Linking also creates the repository's events webhook, or refreshes it if one already points at this connection, for issues, issue comments, pull requests and check runs. The confirmation under the card says whether the webhook was created or updated. If the token cannot manage webhooks, the repository is still linked and the message says what the token is missing.

    Events

    GitHub sends four event types that Flezise classifies:

    EventWhat triggers itAction
    check_run.failureA CI check run failsFix the failing pipeline (fix_ci)
    pull_request.review_requestedA reviewer is requested on a pull requestAddress the review (address_review)
    issues.openedA new issue is createdSync the issue as a work item (sync_issue)
    issue_comment.createdA comment is added to an issueAnswer the question (answer_question)

    Flezise deduplicates deliveries using the x-github-delivery header. Each event is processed at most once.

    Comments written by bots, such as Dependabot or a CI app, are not answered, and neither are the builder agent's own replies, so two bots cannot keep replying to each other. To answer a particular bot anyway, add its account (for example dependabot[bot]) to Bots to answer on the Write-back card, or enter * for every bot.

    The Inbound events card on the detail page controls whether events from this connection can start agent work. Toggle Allow work-item triggers on to enable event-driven work items for this connection.

    Note

    The issues.opened event syncs the issue as a work item only when the project automation policy allows the GitHub provider to create work items. Check Project Settings → Integrations → Automation policy if events arrive but no work items appear.

    FAQ

    The webhook shows a 401 response. What is wrong?

    The signing secret does not match. Copy the Signing Secret from the Flezise connection panel and paste it into the Secret field of the GitHub webhook. The secret must match exactly, with no trailing whitespace.

    No events arrive after I registered the webhook.

    Link the repository again: it re-registers the webhook with the four event types. If you registered it by hand, check that Check runs, Pull requests, and Issues (which covers both issues and issue_comment events) are selected. GitHub does not send events for types not explicitly selected.

    Next steps