How to import a GitHub repo into Replit

The fastest way to import a public GitHub repository is the rapid URL method. In your browser address bar, type replit.com/ followed by the full GitHub repository URL. For example: replit.com/github.com/expressjs/express. Replit automatically detects the language, creates a new Repl, clones the repository, and opens the workspace. This method works for any public repository and requires no configuration. The entire process takes about 30 seconds.

For more control over the import process, use the guided import at replit.com/import. Click 'Import from GitHub' and paste the repository URL. If your GitHub account is not connected yet, Replit will prompt you to authorize via OAuth. Select the repository, choose whether to make the Repl public or private, and click Import. The guided method lets you preview the repository details before importing and is the recommended approach for private repositories.

If OAuth does not work for your organization or you prefer token-based access, create a GitHub Personal Access Token (PAT) and store it in Replit. Go to github.com/settings/tokens, click 'Generate new token (classic),' select the 'repo' scope, and generate the token. Copy it immediately since GitHub only shows it once. In your Replit workspace, open the Tools sidebar, click Secrets, and add a new secret with the key GIT_URL and the value set to your repo URL with the token embedded: https://YOUR_TOKEN@github.com/user/repo.git. This allows Git operations from Shell without re-authenticating.

1# Store this as the GIT_URL secret value in Tools > Secrets:
2https://ghp_your_token_here@github.com/username/private-repo.git
3
4# Then push/pull from Shell using the secret:
5git remote set-url origin $GIT_URL
6git pull origin main
7git push origin main

Imported projects often need a .replit configuration file to tell Replit how to run the app. Enable 'Show hidden files' in the file tree menu to check if one was auto-generated. If not, create a .replit file in the project root. Set the entrypoint to your main file, the run command to start your application, and configure ports if it is a web server. For Node.js projects, the run command is typically 'npm install && npm start'. For Python, it is usually 'pip install -r requirements.txt && python main.py'.

1# Example .replit for a Node.js project
2entrypoint = "index.js"
3run = "npm install && npm start"
4
5[nix]
6channel = "stable-24_05"
7
8[[ports]]
9localPort = 3000
10externalPort = 80

Some imported projects require system packages that are not available by default in Replit. For example, a project using Sharp for image processing needs the vips library. Create or edit the replit.nix file in your project root to declare system-level dependencies. Search for available packages at search.nixos.org/packages. After modifying replit.nix, type 'exit' in Shell to restart the environment and pick up the new packages.

1{ pkgs }: {
2  deps = [
3    pkgs.nodejs-20_x
4    pkgs.nodePackages.typescript-language-server
5    pkgs.python311
6    pkgs.ffmpeg
7    pkgs.imagemagick
8  ];
9}

GitHub repositories often include a .env.example file listing required environment variables. Do not create a .env file in Replit. Instead, open Tools in the left sidebar, click Secrets, and add each variable from .env.example as a Replit Secret. Enter the key name and the actual value for your environment. Replit Secrets are AES-256 encrypted and available as standard environment variables in your code via process.env (Node.js) or os.getenv (Python). RapidDev recommends keeping a .env.example in your repo that lists all required keys without values, so new team members know which Secrets to configure.

1# If .env.example contains:
2# DATABASE_URL=
3# API_KEY=
4# JWT_SECRET=
5
6# Add each as a Replit Secret in Tools > Secrets:
7# Key: DATABASE_URL    Value: postgres://user:pass@host:5432/db
8# Key: API_KEY         Value: sk-your-actual-api-key
9# Key: JWT_SECRET      Value: your-jwt-secret-here

After importing, verify that two-way sync is working. Open the Git pane (Tools > Git) and confirm you see the connected repository URL. Make a small change in Replit, commit it via the Git pane (Agent can auto-generate commit messages), and push. Then verify the change appears on GitHub. Next, make a change directly on GitHub, return to Replit, and pull from the Git pane. This confirms bidirectional sync is fully operational.