[{"data":1,"prerenderedAt":175},["ShallowReactive",2],{"category-git":3},[4,11,16,20,24,28,33,37,41,45,49,53,57,61,65,69,73,77,81,85,89,93,97,101,106,110,114,118,123,127,131,135,139,143,147,151,155,159,163,167,171],{"title":5,"path":6,"acronym":7,"category":8,"difficulty":9,"description":10},".gitignore","\u002Fterms\u002Fg\u002Fgitignore",null,"git","beginner","A .gitignore file is a list of files and folders that Git should completely ignore. It's like telling Git 'pretend these don't exist.",{"title":12,"path":13,"acronym":7,"category":8,"difficulty":14,"description":15},"Blame","\u002Fterms\u002Fb\u002Fblame","intermediate","Git blame shows you who wrote each line of a file and when.",{"title":17,"path":18,"acronym":7,"category":8,"difficulty":9,"description":19},"Branch","\u002Fterms\u002Fb\u002Fbranch","A branch is like creating a parallel universe for your code.",{"title":21,"path":22,"acronym":7,"category":8,"difficulty":9,"description":23},"Branch Cemetery","\u002Fterms\u002Fb\u002Fbranch-cemetery","A branch cemetery is the graveyard of abandoned feature branches in your repo. Hundreds of them. Nobody knows what's on them. Nobody dares delete them.",{"title":25,"path":26,"acronym":7,"category":8,"difficulty":9,"description":27},"Checkout","\u002Fterms\u002Fc\u002Fcheckout","Checkout is like teleporting to a different branch or going back in time to an old version.",{"title":29,"path":30,"acronym":7,"category":8,"difficulty":31,"description":32},"Cherry-pick","\u002Fterms\u002Fc\u002Fcherry-pick","advanced","Cherry-pick is like copying one specific change from another branch without merging everything.",{"title":34,"path":35,"acronym":7,"category":8,"difficulty":9,"description":36},"Clone","\u002Fterms\u002Fc\u002Fclone","Clone is like downloading someone's entire project to your computer — all the files, all the history, everything.",{"title":38,"path":39,"acronym":7,"category":8,"difficulty":9,"description":40},"Commit","\u002Fterms\u002Fc\u002Fcommit","A commit is like pressing the save button in a video game.",{"title":42,"path":43,"acronym":7,"category":8,"difficulty":14,"description":44},"Conflict","\u002Fterms\u002Fc\u002Fconflict","A conflict is when two people changed the exact same part of the same file differently, and Git doesn't know which version to keep.",{"title":46,"path":47,"acronym":7,"category":8,"difficulty":9,"description":48},"Conventional Commits","\u002Fterms\u002Fc\u002Fconventional-commits","Conventional Commits is a format for writing commit messages that humans AND machines can understand.",{"title":50,"path":51,"acronym":7,"category":8,"difficulty":9,"description":52},"Dead Branch","\u002Fterms\u002Fd\u002Fdead-branch","A dead branch is a branch nobody touches anymore. No commits in months, no open PR, no clear purpose. It's just... there. Safe to delete? Probably.",{"title":54,"path":55,"acronym":7,"category":8,"difficulty":9,"description":56},"Diff","\u002Fterms\u002Fd\u002Fdiff","A diff shows you exactly what changed between two versions of your code.",{"title":58,"path":59,"acronym":7,"category":8,"difficulty":9,"description":60},"Fork","\u002Fterms\u002Ff\u002Ffork","A fork is like making your own personal copy of someone else's project on GitHub.",{"title":62,"path":63,"acronym":7,"category":8,"difficulty":9,"description":64},"Git","\u002Fterms\u002Fg\u002Fgit","Git is like a magical save system for your code. Every time you save (commit), it remembers exactly what changed.",{"title":66,"path":67,"acronym":7,"category":8,"difficulty":9,"description":68},"Git Blame Driven Development","\u002Fterms\u002Fg\u002Fgit-blame-driven-development","Git blame driven development is when you look at broken code and your first action isn't to fix it — it's to run `git blame` to find out who wrote it.",{"title":70,"path":71,"acronym":7,"category":8,"difficulty":9,"description":72},"GitHub","\u002Fterms\u002Fg\u002Fgithub","GitHub is like Instagram for code.",{"title":74,"path":75,"acronym":7,"category":8,"difficulty":14,"description":76},"HEAD","\u002Fterms\u002Fh\u002Fhead","HEAD is like a bookmark that says 'you are here' in your Git history. It points to the commit you're currently looking at.",{"title":78,"path":79,"acronym":7,"category":8,"difficulty":9,"description":80},"Log","\u002Fterms\u002Fl\u002Flog","Git log is like a diary of everything that happened in your project. It shows a timeline of all commits — who made them, when, and the messages they wrote.",{"title":82,"path":83,"acronym":7,"category":8,"difficulty":9,"description":84},"Merge","\u002Fterms\u002Fm\u002Fmerge","Merge is like combining two parallel universes back into one. You take the changes from your branch and smoosh them into another branch.",{"title":86,"path":87,"acronym":7,"category":8,"difficulty":9,"description":88},"Merge Hell","\u002Fterms\u002Fm\u002Fmerge-hell","Merge hell is when you've been on a feature branch for three weeks, main has moved 400 commits, and now every file has a conflict.",{"title":90,"path":91,"acronym":7,"category":8,"difficulty":9,"description":92},"Merge Monster","\u002Fterms\u002Fm\u002Fmerge-monster","A merge monster is that one colossal PR that's been open for two months, touches 400 files, and everyone's afraid to merge.",{"title":94,"path":95,"acronym":7,"category":8,"difficulty":9,"description":96},"Origin","\u002Fterms\u002Fo\u002Forigin","Origin is just the default nickname for the remote server where your code lives. When you clone a repo, Git automatically names that remote 'origin'.",{"title":98,"path":99,"acronym":7,"category":8,"difficulty":9,"description":100},"Pull","\u002Fterms\u002Fp\u002Fpull","Pull is the opposite of push — it downloads everyone else's latest changes from the cloud to your computer.",{"title":102,"path":103,"acronym":104,"category":8,"difficulty":9,"description":105},"Pull Request","\u002Fterms\u002Fp\u002Fpull-request","PR","A pull request is like raising your hand in class and saying 'Hey, I made some changes — can someone check my work before we make it official?",{"title":107,"path":108,"acronym":7,"category":8,"difficulty":9,"description":109},"Push","\u002Fterms\u002Fp\u002Fpush","Push is like uploading your saved game to the cloud so your friends can download it.",{"title":111,"path":112,"acronym":7,"category":8,"difficulty":31,"description":113},"Rebase","\u002Fterms\u002Fr\u002Frebase","Rebase is like rewriting history.",{"title":115,"path":116,"acronym":7,"category":8,"difficulty":9,"description":117},"Remote","\u002Fterms\u002Fr\u002Fremote","A remote is the cloud copy of your project — usually on GitHub or GitLab.",{"title":119,"path":120,"acronym":121,"category":8,"difficulty":9,"description":122},"Repository","\u002Fterms\u002Fr\u002Frepository","Repo","A repository (repo) is a folder that Git is watching. It contains all your project files plus the entire history of every change ever made.",{"title":124,"path":125,"acronym":7,"category":8,"difficulty":31,"description":126},"Reset","\u002Fterms\u002Fr\u002Freset","Reset is like pressing undo on your commits.",{"title":128,"path":129,"acronym":7,"category":8,"difficulty":14,"description":130},"Revert","\u002Fterms\u002Fr\u002Frevert","Revert is the safe undo button. Instead of erasing history (like reset), it creates a NEW commit that undoes the changes from an old commit.",{"title":132,"path":133,"acronym":7,"category":8,"difficulty":14,"description":134},"Sparse Checkout","\u002Fterms\u002Fs\u002Fsparse-checkout","Sparse checkout lets you clone only specific folders from a repo — grocery shopping with a list instead of buying the whole store.",{"title":136,"path":137,"acronym":7,"category":8,"difficulty":14,"description":138},"Squash","\u002Fterms\u002Fs\u002Fsquash","Squash is like combining multiple save points into one.",{"title":140,"path":141,"acronym":7,"category":8,"difficulty":9,"description":142},"Staging Area","\u002Fterms\u002Fs\u002Fstaging-area","The staging area is like a shopping cart. Before you 'buy' (commit) your changes, you put them in the cart first with `git add`.",{"title":144,"path":145,"acronym":7,"category":8,"difficulty":9,"description":146},"Stale Branch","\u002Fterms\u002Fs\u002Fstale-branch","A stale branch is one that's fallen behind main so much that merging it back in is going to hurt. A branch goes stale in hours on fast-moving teams.",{"title":148,"path":149,"acronym":7,"category":8,"difficulty":14,"description":150},"Stash","\u002Fterms\u002Fs\u002Fstash","Stash is like putting your messy work in a drawer temporarily.",{"title":152,"path":153,"acronym":7,"category":8,"difficulty":31,"description":154},"Submodule","\u002Fterms\u002Fs\u002Fsubmodule","A submodule is a repo inside another repo. It's like embedding someone else's project inside yours.",{"title":156,"path":157,"acronym":7,"category":8,"difficulty":14,"description":158},"Tag","\u002Fterms\u002Ft\u002Ftag","A tag is like a permanent bookmark on a specific commit. While branches move forward as you add commits, a tag stays put forever.",{"title":160,"path":161,"acronym":7,"category":8,"difficulty":14,"description":162},"Trunk-Based Development","\u002Fterms\u002Ft\u002Ftrunk-based-development","Instead of giant feature branches that live for 3 weeks and cause merge hell, trunk-based development has everyone commit to main every day.",{"title":164,"path":165,"acronym":7,"category":8,"difficulty":31,"description":166},"Worktree","\u002Fterms\u002Fw\u002Fworktree","A worktree lets you have multiple branches checked out at the same time in different folders.",{"title":168,"path":169,"acronym":7,"category":8,"difficulty":9,"description":170},"Zombie Branch","\u002Fterms\u002Fz\u002Fzombie-branch","A zombie branch is a merged branch that's still lying around in your repo, refusing to stay dead. It got merged weeks ago. The PR is closed.",{"title":172,"path":173,"acronym":7,"category":8,"difficulty":9,"description":174},"Zombie PR","\u002Fterms\u002Fz\u002Fzombie-pr","A zombie PR is one that's technically still open but the author left the company six months ago, the branch conflicts with everything, and the feature was...",1776518250072]