Loading...
Pushing a Project to GitHub
Sending your project's files to a repository you own, and the secret files the push leaves out on purpose.
What the push sends
A push sends your project's files to the repository you choose. They are the same files the editor works from, with one difference: anything in them that looks like a secret — a bot token, an API key — is blanked out on the way, replaced by a marker such as ${REDACTED_…}. So a file with a key typed into it arrives on GitHub without the key, and the GitHub copy is not an exact copy of your file tree. Each file is written to the repository in turn, and the message at the end says how many went up: "Pushed 12 files.", or "Created owner/repo and pushed 12 files." for a new repository, with a link to the repository beside it.
Some files are held back on purpose. Secret files — a .env and its relatives — are never pushed, and that same message counts them for you. Images and other binary files go up as their real bytes.
A project with nothing to send is refused rather than pushed empty: you get "This project has no files to push". More than 2000 files is refused as well.
Other ways to get your code out
A push is not the only route out of VyroAI:
- Download the project. The Build & Export menu has Download Source (.zip), and the file tree has a Download on any single file. Unzip it into a local clone and commit it yourself.
- Publish the project if the point was to let someone else read it, and turn on Source Code (.zip) so visitors can download the source. See Community & Sharing.
For rolling back your own work, Version History inside VyroAI is the tool, not GitHub.
It is a one-way push
The word sync usually means more than this does, so know what you are getting:
- There is no pull — nothing comes back from GitHub into your project
- There is no branch choice
- There is no merge, so anything changed on GitHub can be overwritten
- The commit message is always Sync from VyroAI
It is publishing a copy, not version control.
Your .env is left behind on purpose
The push does not send secret files. A .env, any .env.<name> that is not an example or a template, key and certificate files (.pem, .key, .p12, .pfx), SSH keys, credentials.json, service-account.json and anything whose name starts with secrets. are all held back.
That matters most for Discord bots, because saving your bot token in the Bot Console writes DISCORD_TOKEN=… into .env. That file does not reach the repository, public or private, and you do not have to clear the token by hand first.
The message after a push says how many were withheld — "1 secret file was left out on purpose (.env and similar)." — so a missing .env on GitHub reads as deliberate, not lost. See Bot Token & Inviting Your Bot.
Where the controls are: connect GitHub under Profile → Connectors, then open the project's Connectors section in Project Settings (it used to be called the GitHub tab). There is no Owner box: your GitHub name is read from the connected account and shown in grey. Pick one of two ways in:
- Create a new repository — the name is filled in from the project, the Private repository switch starts on, and Create and push makes the repository and pushes into it.
- Use one I already have — pick one of your repositories from the list and press Push to <repo>.
Also in Code Studio (IDE)
- Next in Code Studio (IDE): Adding & Moving Files
- Starting out: Starting a New Project — Four ways to start a project: Quick Create, AI Guided, Advanced Mode and Import from ZIP. Which one suits you, and why simpler project types show three.
- Starting out: Your Projects List — The sidebar, finding a project again, and the defaults every new project starts with.
- Starting out: Project Settings — The gear icon in the Code Studio: per-project AI model and rules, build tool, Java and Minecraft version, publishing and connectors, by project type.
- Starting out: Editor & Themes — Set up the Code Studio editor your way: Monaco or the Simple Editor, font, size, tab width, word wrap and minimap, plus Dark, Light and High Contrast.
27 of 37 in Code Studio (IDE) · Last checked 18 September 2026 · Previous: Importing from GitHub