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

    • Pull requests

    When the builder agent delivers a code change, Flezise opens a pull request on the connected repository. The title and body are generated from the approved story and the diff, not copied from a fixed template.

    What Flezise writes into the PR

    A governed pr-description prompt receives the story content, a summary of diff statistics, and the list of changed files. The generator produces a title and a description that explain what the change does and why.

    If description generation fails (timeout or network error), the PR body falls back to Implementation of story on branch <branch>.

    The PR opens as a draft by default and targets the main branch unless the repository's delivery configuration specifies a different base.

    Note

    Flezise does not read a repository's own pull_request_template file. The PR body always comes from the pr-description generator.

    Generated descriptions apply to every Git provider that supports PR creation: GitHub, GitLab, and Bitbucket.

    CI autofix

    When CI checks fail on the PR branch, Flezise can run a bounded fix loop to address them. This loop is opt-in and off by default.

    The loop is GitHub-only. Providers that do not support CI check polling are skipped immediately, and the loop records a skip reason without attempting a fix.

    Each fix round follows this sequence:

    1. Wait for all CI checks on the PR branch to reach a completed state.
    2. Collect the names of failing checks and, on GitHub, any PR review comments already posted.
    3. Run a sandbox session with the failure context as input.
    4. Commit any changes as fix: address CI failures (round N) and push to the same PR branch.
    5. Poll CI again.

    The loop runs up to two rounds. If checks still fail after two rounds, or if the agent produces no file changes in a round, Flezise escalates: it posts a comment on the work item and sends a notification so a person can take over.

    There is no UI toggle for CI autofix. Enable it by setting ci_feedback_enabled in the project's pipeline configuration.

    Next steps