Get to GitHub: Overview
Why you need GitHub and how to get there from any AI coding tool.
If you're using FinishKit through the MCP server or SDK, your code doesn't need to be on GitHub for local analysis with Intelligence Packs. This section is for cloud scans via the dashboard, or for developers who haven't set up version control yet.
FinishKit cloud scans need your code in a GitHub repository. If you built your app with an AI tool, your code might still be sitting inside that tool's environment.
This section walks you through getting your code to GitHub, tool by tool.
Why GitHub?
GitHub is where your code lives permanently. AI tools are editors. They let you build things, but they're not where your code should live long-term. Putting your code on GitHub means:
- You can connect it to FinishKit for scanning
- You can deploy it to Vercel, Railway, Render, etc.
- You have a backup and a full history of changes
Choose your tool
Prerequisites for all tools
Before pushing to GitHub, you'll need:
- A GitHub account (free)
- Git installed on your machine. Download from git-scm.com if you're using a local tool like Cursor or Windsurf.
If you're using a browser-based tool (Lovable, Bolt, Replit, v0), you don't need to install Git. These tools handle it for you.