Git, and Working Like a Developer
The version control segment that does not stop at commit and push. You make a history on purpose, read it backwards to find when something changed, hit a merge conflict nobody warned you about, and then spend a whole module getting work back after you have destroyed it.
- trending_upBeginner
- schedule7h 47m
- menu_book12 节课程
- publicEnglish
- workspace_premiumBasic
课程概述
You have written programs. They live in a folder, and the folder holds exactly one version: the last one you saved. That is where this segment starts. You will make a repository, commit to it deliberately rather than in a panic at the end of the day, and write messages that mean something to a stranger six months from now. You will read a history backwards to find the single commit that changed a number nobody meant to change. You will branch, and you will hit a merge conflict before anybody explains what one is, because that is when the markers in the file finally make sense. Then module 3, which is the reason this segment exists. You committed a key. You committed to the wrong branch. You lost an afternoon of work and the log does not show it. You pushed something wrong and other people already have it. Four recoveries, each one caused on purpose, each one with the exact output, and every destructive command shown with the thing that gets it back in the same lesson. No account anywhere is needed. The remote you push to is one you create yourself, on your own machine, in a folder next door. By the end you will not have memorised git. You will be able to say what state a repository is in, and get it out of that state, which is the actual job.
课程大纲 · 4 个模块
lock解锁权限内容- 01 A History You Made on Purpose3 节课程·1h 23m
Git records what you tell it to record, when you tell it. It is not a backup that runs in the background. Everything good about a history comes from somebody deciding where one commit ends and the…
- 02 Branches, and the Merge That Stops Halfway3 节课程·1h 52m
Branching is cheap and merging is not frightening. What is frightening is the first time git stops in the middle of a merge and leaves a file full of chevrons, and that happens to you in 2.2 with no…
- 03 The Four Recoveries4 节课程·3h 15m
You are going to work in repositories where other people's work lives. Every destructive command in this module is shown with the thing that gets it back, in the same lesson, because a command you…
- 04 Working Like a Developer2 节课程·1h 17m
The commands stop being the hard part after module 3. What is left is the part that gets you invited back: small changes, honest messages, and a repository that explains itself.
常见问题
- 我将在 Git, and Working Like a Developer 中学到什么?
- The version control segment that does not stop at commit and push. You make a history on purpose, read it backwards to find when something changed, hit a merge conflict nobody warned you about, and then spend a whole module getting work back after you have destroyed it.
- 我需要有先前的经验吗?
- 不需要 — Git, and Working Like a Developer 从基础开始,适合初学者。
- Git, and Working Like a Developer 需要多长时间?
- Git, and Working Like a Developer 包含 4 个模块和 12 节课程。您可以按自己的速度学习。
- 我如何获得访问权限?
- Git, and Working Like a Developer 包含在任何付费订阅中。