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 cd anywhere; it uses files from the active mode/tabs
    • GitHub Integration: Uses your GitHub token (set in Settings) for push operations
    • Available Commands: Type help in 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
    1. Manually create an empty repo on GitHub (no README)
    2. 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 status and log to verify staged and committed files
    • Command Support: If a command isn't recognized, type help for the supported subset