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

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, the Inbound events card with Allow work-item triggers toggle, and the Link repository button

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 repo and workflow scopes for CI events to arrive.

Once connected, copy the Webhook URL from the connection panel and register it in your repository or organization settings under Settings → Webhooks. Set the content type to application/json and paste the Signing Secret from the same panel into the webhook's secret field.

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, link a repository so the builder agent knows where to clone and push. Press Link repository on the detail page and enter the repository in owner/name format.

A connection's optional Repository config field sets a default repository for automation. When set, the builder agent targets that repository without requiring an explicit choice for each run.

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.

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.

Check that you subscribed to the four event types: Check runs, Pull requests, and Issues (which covers both issues and issue_comment events). GitHub does not send events for types not explicitly selected.

Next steps