Quick Reference for Farmers --- 30+ terms with plain-language definitions and farm analogies
| Term | Definition | Farm Analogy |
|---|---|---|
| Repository (Repo) | A folder that holds all your project files, history, and settings | Your farm office filing cabinet |
| README | A document at the top of a repository that explains what the project is about | The sign on the barn door |
| Issue | A task, bug report, or feature request tracked in a repository | A work order pinned to the bulletin board |
| Label | A color-coded tag you attach to an Issue to categorize it | Color-coded flags on work orders (red = urgent) |
| Milestone | A group of Issues tied to a target date or goal | A seasonal goal ("Spring Planting Complete by May 1") |
| Project | A planning board that organizes Issues into views like Board, Table, and Timeline | Your farm planning wall |
| Board View | A Project view with columns (To Do, In Progress, Done) | A corkboard with swim lanes |
| Table View | A Project view that looks like a spreadsheet | A ledger or spreadsheet |
| Timeline / Roadmap View | A Project view that shows Issues on a calendar | The farm calendar on the wall |
| Custom Field | An extra column you add to a Project (Priority, Season, Cost) | Extra columns on your planning sheet |
| Iteration | A repeating time block for planning work (weekly, biweekly, monthly) | A work sprint --- "This week's jobs" |
| Pull Request (PR) | A proposal to merge changes from one branch into another | Handing your work to the boss for review before it's final |
| Branch | A separate copy of the code where you make changes without affecting the main version | A test plot where you try new seeds before planting the whole field |
| Merge | Combining changes from a branch back into the main version | Moving what worked in the test plot to the full field |
| Commit | A saved snapshot of your changes with a description of what you did | Signing and dating an entry in the farm log |
| Fork | A personal copy of someone else's repository | Making a photocopy of a neighbor's planting plan to customize |
| Clone | Downloading a repository to your local computer | Taking the plans home from the office |
| Notification | An alert from GitHub about activity in your repositories | The farm radio squawking when something needs attention |
| Watch | Subscribing to a repository so you get notifications about its activity | Tuning in to a specific radio channel |
| @mention | Tagging someone by name to get their attention in a comment | Calling someone by name over the radio |
| Discussion | A conversation thread in a repository for open-ended topics | The break-room whiteboard for ideas and questions |
| Template | A pre-built form or structure you reuse for new Issues or repositories | A pre-printed work order form |
| Issue Template | A fill-in-the-blank form that appears when someone creates a new Issue | A blank work order with sections already labeled |
| YAML | A structured text format used for configuration files and workflows | A recipe card with labeled ingredients and steps |
| GitHub Actions | An automation system that runs tasks when something happens in your repository | An automatic irrigation timer that runs on a schedule |
| Workflow | A set of automated steps defined in a YAML file | The irrigation schedule --- which zones, when, how long |
| Trigger | The event that starts a workflow (e.g., new Issue created, PR opened) | The timer clicking on --- what starts the irrigation |
| GitHub Copilot | An AI writing assistant that suggests text based on your instructions | A farmhand who finishes your sentences |
| Prompt | The instruction you give an AI tool to tell it what you need | Telling the farmhand what you want written |
| Draft | The text or output an AI tool generates for you to review | The farmhand's first attempt --- needs your review |
| Evaluate | Checking AI output for accuracy, completeness, and relevance | Inspecting the farmhand's work before signing off |
| GitHub Spark | A tool that builds simple web apps from plain English descriptions | A farmhand who builds a tool from your sketch |
| Agent | An AI that follows multi-step instructions autonomously | A farmhand who handles a full job list |
| Human-in-the-Loop | The principle that a person reviews AI work before it takes effect | Checking the farmhand's work before it's final |
| Guardrails | Limits on what AI can do without permission | A fence keeping the farmhand in the right pasture |
| Approval Gate | A checkpoint where AI pauses and waits for your go-ahead | The farmhand asking permission before buying parts |
| Markdown | A simple text formatting language used in GitHub (headings, bold, lists, checkboxes) | Formatting a letter with headings and bullet points |
| Checkbox | A clickable box in an Issue that tracks completion (- [ ] in Markdown) |
Checking items off a to-do list |
| Assignee | The person responsible for completing an Issue | The farmhand assigned to a specific job |
| Status | Where an Issue or task is in the workflow (To Do, In Progress, Done) | Whether a job is waiting, underway, or finished |
| Organization | A shared GitHub account for teams to collaborate | The farm business entity that everyone works under |
Keep this glossary handy as you work in GitHub. Terms are listed in the order you'll encounter them across Sessions 1-12.