Rullst AcademyRullst Academy/Lesson
Git: every change counts · Lesson 09 / 10

Connect without confusing roles

Your local history can gain a remote copy. Before sending, choose destination, visibility and which data you intend to share.

Learning paths16 min

Let's discover together

  1. 1

    A remote is a named destination; origin is conventional, not a special service. git remote -v lists destinations. git clone creates another folder with a repository copy and normally configures origin. Do not init inside a clone.

  2. 2

    fetch receives objects and updates remote references without integrating into the current branch itself. pull receives and integrates according to options; pull --ff-only here refuses divergence. push sends authorised local commits; saving or committing is not pushing.

  3. 3

    Real publishing is optional and uses your own authorised account. The guide below starts with an empty private repository and browser authentication using GitHub CLI. Your Rullst Academy password does not authenticate Git; Rullst Academy login and publishing authorisation are separate flows too.

  4. 4

    If push is rejected because remote commits are missing locally, stop and inspect fetch and log. Do not use push --force blindly. The workshop tests this with a fictional local remote, without external accounts.

GIT · .md

Your change laboratory

This page’s experiments show prepared outputs. To run real commands, use a new practice folder on your computer and the guide included in “Download activity”. Read the instructions before each command.

My files and GitHub

The editor below saves your Markdown notes in this browser. Download a copy to take them to another device. Sending that file to GitHub does not send your computer’s .git history.

FROM LESSON TO PRACTICE

A guide to follow at your pace

Read the steps before using the reference below. Commands run in the indicated system’s terminal; signup happens on the official site. Rullst Academy exercises are practice and do not verify your installation or external account.

git remote -v
git fetch origin
git log --oneline --graph --all
# Only with clean status and compatible history:
git pull --ff-only

Official links and next step

✦
YOUR MISSION

Distinguish clone, remote, fetch, pull and push; share optionally.

Now it's your turn

Discovery workshop

Read the state, choose the next step

In this reduced example, main is at Start and another copy pushed Add tip to remote origin. fetch receives the update; we compare HEAD and origin/main afterwards. We show only log query results, without transfer messages. Prepared outputs; this page does not connect to GitHub.
Mini experiment

Learning simulation: compare cards and check your predictions. The browser is not compiling Rust or starting a server.

git fetch origin
git log -1 --format=%s HEAD
Build your answers and check when you are ready.
A moment to understand

Does fetch alone alter your working branch?

I need a hint

Receiving information and integrating changes are different steps.

Loading your journey…

Take it with you

Use the final guide local-remote exercise or optionally publish to your private repository. Check URL and history before sending; do not include credentials or private paths in your notebook.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.