Clone a GitHub Repository
If your bot is a Java .jar , you do not need to clone a Git repository. Just upload the .jar file to your server. There are two ways to clone your GitHub repo
Updated Jul 7, 2026
If your bot is a Java .jar, you do not need to clone a Git repository. Just upload the .jar file to your server.
There are two ways to clone your GitHub repository:
- On server creation: Select GitHub as the source, as explained in Set Up a Server.
- Files tab: Click the GitHub icon in the options bar, then follow the steps.
Choose the repository type:
- Private: Requires a GitHub account connection. Select the repository and branch if the account is already linked.
- Public: Requires a GitHub repository link.
Private repositories require access to the target repository. If it does not appear in the list, reconnect GitHub and confirm the account can read that repository.
Choose the sync strategy:
- Replace all files: Removes everything already present on the server. Use this for a clean deployment.
- Merge: Keeps existing files and overwrites files with the same name and location from the repository. Use this to update an existing setup.
- Add in subfolder: Clones files into a subfolder. Use this when the repository is only part of your server files.
Finally, click Sync and wait for the server to finish cloning.
Troubleshooting
- Repository does not appear: Reconnect GitHub, then check that the account has access to the repository.
- Wrong files were imported: Confirm the selected branch and sync strategy, then run the sync again.
- Clone fails: Verify the repository link, make sure the repository still exists, and confirm GitHub is reachable.