access to the code backend
Source Control tab
… where you click to access Commit / Changes options
this is also where your files waiting to commit/stage/changed will display
The flow works like this:
- A file is edited = Changes (this gonna show on that section)
- Staged = when you mark a file that you believe is ready to commit
- Commit = Staged files will be grouped on a saved “Source Control Graph” which is your Commit History. Think like a game save point with all progress you had until that point.
When the prototyper finishes creating the new app (overwriting yours) he’ll commit these changes, that’s why you need to revert it. So you can restore your app to a previous save point (commit in the codding jargon)
So you basically need to undo commits and changes the new prototyper made to your files. That’s it.
Here is displayed all the info you need about source control, previous commits, sync information, etc
These blue and purple dots are commits (save points) that gemini automatically does every time he finishes a response successfully.
Once you have a github account linked to the code interface <>
- purple will represent commited changes synced to the github cloud server (think it as your google drive/dropbox for codding projects)
- Blue are commits that aren’t yet synced to the cloud, that’s why the purple sync button is showing
the github part (setting up account, etc) is trickier, but there are plenty tutorials on youtube for beginners. You really don’t need it, but it’s a extra feature that will make sure you have your project save points (commits) saved to a cloud service which reduces greatly the chance of you losing it.
hope this helps. if you need further details let me know