GitHub for Non-Developers: Don't Lose Your App

What GitHub is in plain English

GitHub is an online home for your project’s files and its history. It is not the app itself, and it is not a backup of every service your app uses, but it gives you a record of code changes you can inspect and return to.

Repository = the project’s online home
Commit = a named save point in the project history
Push = send your local commits to GitHub
Pull = bring newer commits from GitHub into your local project
Branch = a safe experiment that starts from a known point
Diff = the exact lines that changed

The five actions to remember

Before asking an AI tool to edit code, create a clear checkpoint. After the tool makes a small change, review the diff and run a focused test before creating another checkpoint.

A commit is not a guarantee that the whole app is safe, and GitHub does not protect database rows, payment settings, environment variables, or uploaded files by itself. Treat it as one part of recovery.

Before a risky change: check status and commit known-good work
After a change: inspect the diff before committing
Before pulling: make sure your local work is saved or intentionally set aside
When unsure: stop and ask for a read-only report

Before Claude or Codex changes code

Give the AI a narrow task and a clear boundary. This makes both the change and the review easier.

Ask for an audit first; do not begin with “fix everything”
Tell it which files or feature are in scope
Say what must not change
Ask for one change at a time
Require tests and a final diff summary
Never paste secrets into a prompt or commit them

When GitHub Desktop shows conflicts

A conflict means two versions changed the same area and Git cannot safely choose. It is not proof that your app is lost. Do not click through every “accept” option without understanding which behavior you are keeping.

Pause, save a screenshot or copy of the conflict, and ask for a plain-English explanation. Decide whether the local or incoming behavior is correct for each conflict, then test the resulting workflow.

Do not delete the conflicted files
Do not reset or force-push as a first reaction
Resolve one file or behavior at a time
Run the app and a focused test after resolving
Commit only after the conflict is gone and the diff makes sense

Emergency recovery checklist

Stop making new changes
Record the current branch and Git status
Save any important uncommitted text outside the editor
Inspect recent commits and the current diff
Identify the last known-good commit
Check whether the problem is code, environment, database, or deployment
Choose the least destructive recovery option
Test after recovery before continuing
If secrets may be exposed, rotate them and review history
Write a short recovery note for the next session

Copy-paste prompt for Codex

Prompt 51

Read-only GitHub inspection

Copy-paste prompt

Inspect my project’s Git status safely. Report the current branch, recent commits, changed files, untracked files, and whether the working tree is clean. Do not commit, reset, checkout, merge, push, pull, delete files, or change history. If anything is unclear, stop and explain it in plain English.

This prompt deliberately limits the AI to inspection.