Base44 imports existing GitHub repositories and ships changes back as pull requests

Archive entry: this covers an event from August 19, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On August 19, 2026, Base44 let users import an existing GitHub repository, change it through AI chat and send the changes back as pull requests, as the Base44 product changelog records.

What the GitHub import included

• Base44 imported a GitHub repository and let users work on it like any other app, in a cloud environment with no local setup.
• Users asked for changes in AI chat and saw them live in the preview.
• Changes went back to the repository as a pull request, so the repository stayed the source of truth.
• Private repositories connected through the user's own GitHub sign-in.
• On the same day, branches became full copies of an app with their own preview and version history, and branches could be created on any GitHub-connected app.

What it meant for people building with Base44

Base44 moved beyond greenfield apps into existing codebases. A project that already lived in a GitHub repository could be brought into Base44 and changed through chat with a live preview, while the repository stayed the source of truth because changes returned as pull requests. Private repositories were covered too, through the user's own GitHub sign-in.

Base Code and credits

Subsequent changelog entries called this workflow Base Code. From September 28, 2026, the first build in an app imported with Base Code cost no credits.

Sources

• Product changelog: Bring an existing GitHub project into Base44 (Base44, August 19, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.