Code execution for this mode is not supported in the browser. Use the Chat panel or assistant interface to get feedback.
Console Output
$
Files
π§ Git Workflow
π How the Git Terminal Works
- Virtual Workspace: Operates on the current mode's files (Web, Pascal, Python, Node JS/TS)
- No Navigation: You don't need to
cdanywhere; it uses files from the active mode/tabs - GitHub Integration: Uses your GitHub token (set in Settings) for push operations
- Available Commands: Type
helpin the Git panel to see supported commands
βοΈ Prerequisites
Required: Open Settings (βοΈ gear button) β paste your GitHub Token β Save β Test
This is required for push operations to work.
π Typical Workflow
Step 1: Initialize repo and stage files
Open the Git panel (right-side "Git" tab) and run these commands:
# Initialize a repo for the current mode's files
init
# See what's tracked
status
# Stage everything from the current mode
add .
Step 2: Commit your changes
commit -m "Initial commit"
Step 3: Set main branch (if needed)
branch -M main
Step 4: Create remote and push
Option A: If create-repo is supported
# Create a GitHub repo and set it as origin
create-repo my-learning-project --private
push -u origin main
Option B: Manual repo creation
- Manually create an empty repo on GitHub (no README)
- Then run:
remote add origin https://github.com/<your-username>/<your-repo>.git
push -u origin main
π Important Notes
-
Mode-specific files: Current mode determines what gets added/committed
- Web β HTML/CSS/JS tabs
- Python β .py editor content
- Node β JS/TS file content
- Node run result: In Node (JS/TS) modes, the Run Result shows only the console output; the iframe preview is hidden.
- Verification: Use
statusandlogto verify staged and committed files - Command Support: If a command isn't recognized, type
helpfor the supported subset