Home / Flashcard library / General knowledge / Vibe coding / Git and Safety Nets

General knowledge

Vibe Coding — Git and Safety Nets flashcards

10 of 70 cards free to study here · 5 topics · the whole deck is built into Willys

Git for builders (commits, branches, diffs, log, revert and restore), committing before big changes, .gitignore, pull requests and review, CI as an automatic checker, environment variables and .env files, leaked secrets and backups.

Get the app All Vibe coding decks

Learn deck · part of Vibe coding · written against: Building software with AI assistants: workflow, prompting, git, web basics, debugging and security; tool-neutral. Updated 2026-10-10.

Study the free sample

10 cards from the deck as they are. Flip, rate yourself, filter by topic; your progress stays in this browser.

The 10 sample cards as a list
  1. What is git, in one sentence?
    A version control system: it records snapshots of your project over time so you can see what changed, when, and go back to earlier versions.
    Git Basics › Repositories and Commits
  2. What is a git repository?
    A project folder that git tracks, with its full history kept in a hidden .git folder inside it.
    Git Basics › Repositories and Commits
  3. What is a git branch?
    A separate line of development, really a movable pointer to commits, so you can try changes without touching the main version.
    Branches and Undo › Branches
  4. What does git switch -c try-dark-mode do?
    It creates a new branch named try-dark-mode and switches to it in one step.
    Branches and Undo › Branches
  5. What is a pull request?
    A request on a hosting platform to merge one branch into another, showing the diff and giving a place to discuss and review it first. Some platforms call it a merge request.
    Collaboration and CI › Pull Requests and Review
  6. Why open a pull request even on a solo project?
    You get one clean diff to review, and a natural point for automatic checks to run before anything reaches main.
    Collaboration and CI › Pull Requests and Review
  7. What is an environment variable?
    A named value set outside your code, in the environment the program runs in, which the code reads at run time. Often used for settings and secrets.
    Secrets and Configuration › Environment Variables
  8. Why keep API keys in environment variables instead of in the code?
    Code gets shared, committed and copied. Environment variables stay on the machine or hosting platform, so the secret doesn't travel with the code.
    Secrets and Configuration › Environment Variables
  9. Is a git repository that lives only on your laptop a backup?
    No. If the laptop dies, the repository goes with it. Push to a remote, such as a hosting platform, so a copy lives somewhere else.
    Backups › Backup Habits
  10. Your only copies of a project are a laptop and a USB stick that travel in the same bag. What does the 3-2-1 rule say is missing?
    An off-site copy (and a third copy). The rule is 3 copies, 2 kinds of storage, 1 somewhere else; one stolen bag takes both of yours.
    Backups › Backup Habits

Unlock the whole deck

You are studying a free 10-card sample. All 70 cards of Vibe Coding — Git and Safety Nets, the other 5 Vibe coding decks, and spaced-repetition scheduling are built into Willys. 14-day free trial, then $14.99 a year.

Get the app

In Willys, tap Exam Library at the top of your Decks (or Browse Exam Library… under the + button), find the exam on its shelf or by search, tick it and tap Add.

More Vibe coding decks

FoundationsPrompting and ContextWeb Basics for BuildersDebugging and SecurityPractice Questions

← All Vibe coding decks, with the study guide and topic outline.

About these cards

Review status: Second-reader reviewed, with corrections applied.

Checked against:

  • Original material; checked against the Git documentation, Pro Git (2nd edition, CC BY-NC-SA 3.0), GitHub Docs (CC BY 4.0), GitLab Docs (CC BY-SA 4.0), MDN Web Docs (CC BY-SA 2.5), the OWASP Cheat Sheet Series (CC BY-SA 4.0), Google's Engineering Practices documentation (CC BY 3.0), The Twelve-Factor App (MIT), the Python documentation (PSF License), the npm documentation, the Node.js, ESLint and Laravel documentation (MIT), the dotenv README (BSD-2-Clause), US-CERT's Data Backup Options (2012) and NIST SP 800-34 Rev. 1 (US government work); reference only, no text copied

These are independent study notes written for Willys. They are not official exam material, may contain mistakes, and are no substitute for your course, your teacher or the exam owner's own publications. Found an error? Tell us — corrections ship as a new version of the deck.

Use of these pages is covered by our Terms of Use.