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/tutorials/existing-codebase.md.
Docs
  • 26.11

    • Bring an existing codebase

    This tutorial brings Saleor, an open-source commerce platform split across three repositories, into Flezise and takes it as far as a pull request that fixes a real bug. Pick a chapter to jump straight to it.

    What each chapter shows

    1. Connect your code. Choose Existing codebase, add each repository, describe how they fit, and press Connect & continue. Read more in Import a codebase.
    2. Run the setup interview. Start the interview from the Ready checklist while the code is scanned, and answer Atlas's questions about the change you want and what must keep working.
    3. Check the baseline. Open the audit report, review the known failures and the coding standards, and press Accept baseline.
    4. Connect your systems. Link a GitHub repository, turn on Jira's work-item triggers, copy its webhook address, and allow Jira in the automation policy. Read more in Integrations.
    5. Add your team's knowledge. Upload documents, search them in the Knowledge Base, and ask Atlas a question that it answers from your documents and code. Read more in Knowledge base.
    6. From Jira ticket to pull request. Assign a ticket to Atlas, approve its plan, and review the pull request and its test runs before you press Accept changes. Read more in Review a fix.
    7. Atlas in Slack. Mention Atlas in a channel to ask about your system, or ask it to log a bug, which lands on the board as a work item. Read more in Slack.