Git setup, clone & push

Check your Git installation

Install Git on the machine where commands will run. For SSH workspaces and development containers, that means the remote host or container. Configure the author details you want recorded in your commits.

git --version
git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Before you continue: These commands change your global author identity. Use repository-local configuration instead if you need different details for this project.

Authenticate with a personal access token

Use your Ramuvo username when Git asks for a username. Keep the token out of clone URLs, shell history, committed files, and screenshots. A credential helper can store it for terminal Git; choose one appropriate to your operating system.

1. Open Settings → Personal access tokens.
2. Choose the smallest repository, capability, branch, and path access that your task needs, where those controls are available.
3. Set an appropriate expiry and generate the token. Complete reauthentication if requested.
4. Copy it immediately; it is shown once. Use the token as the Git HTTPS password.

Clone a repository

Copy the HTTPS clone URL from the repository. Substitute your own owner and repository in this example.

git clone https://ramuvo.com/git/OWNER/REPOSITORY.git
cd REPOSITORY
git status

Push committed changes

Review the staged files before committing. Push sends commits, not unsaved editor changes. Use your actual branch name. If an existing repository has commits you do not have, fetch and review them before integrating; do not force-push as a routine fix.

git status
git add path/to/changed-file
git commit -m "Describe the change"
git push -u origin main

When authentication or a push fails

Check token expiry, account access, repository capability, branch/path restrictions, and the exact push URL. A browser login alone does not authenticate terminal Git. Git LFS projects also need Git LFS installed on the command host.