Share & review code

Books matched to this capability.

5books in this track

L01 · User

Who is affectedOnly you
T19-L01

Keep Your Files in Gitea and Get Any Version Back

Put a file into a private Gitea repository, check each change in red and green before you save it, read its history, open old versions and take one change back with Revert, all in the browser.

Outcome: A private Gitea repository whose main file has at least four commits in its History, including one revert; every message says why, and you can show the red-and-green view of one change and the earlier version within a minute.

User15 minLast edited: Sep 25, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T19-L02

Work on a Shared Gitea Repository From Your Computer With OpenCode

Connect your computer to Gitea with an SSH key, copy a repository down, commit, push and pull with OpenCode, give a colleague access, and stop OpenCode from settling a conflict on its own.

Outcome: A shared repository with a commit pushed from your computer under your name, a colleague's Gitea commit pulled to your computer, a .gitignore for raw data, and one same-line conflict stopped by OpenCode and decided by the two of you; every message says why.

Power user15 minLast edited: Sep 25, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T19-L03

Propose, Review and Merge Changes With Pull Requests

Protect main so nothing reaches it unread, record a problem as an issue, propose the fix as a pull request, review it line by line, and merge it so the issue closes by itself.

Outcome: A protected main, an issue and a merged pull request that fixes it, with at least one line comment, one Request changes, a new commit answering it and an Approve; the merge closed the issue, and a direct push to main is refused.

Builder15 minLast edited: Sep 25, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T19-L04

Check Every Change Automatically, Release Versions and Tell the Lab

Run an automatic check on every pull request with Gitea Actions, make it required so a failing change cannot be merged, keep the chat address as a secret, and publish numbered releases that announce themselves in the lab chat.

Outcome: A repository where a required automatic check runs on every pull request, one pull request was blocked by it and fixed, and publishing release v1.0 posted a message in the chat using the secret address.

Integrator18 minLast edited: Sep 25, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T19-L05

Run Your Organisation's Gitea: Teams, Safe Sign-In and a Restore You Have Tested

Move the lab's repositories into an organisation with teams, add two-factor and institute sign-in, mirror to GitHub, back up the whole Gitea, prove the restore on a separate test server, and hand over with a one-page runbook.

Outcome: A colleague restores last night's backup on a test server using only the runbook and finds the organisation with its repositories, issues and pull requests; every password account has two-factor, a student account can read but not edit, and the mirror updated within the last day.

Operator22 minLast edited: Sep 25, 2026