git-novice
git-novice copied to clipboard
swcarpentry
Version Control with Git
Currently the lesson is really overloaded (too much material/too many concepts), and generally teaches bad/dangerous practices (e.g. the conflicts and remote sections are going to cause grumpy collaborators, and while...
In Episode 4, ["Tracking Changes"](http://swcarpentry.github.io/git-novice/04-changes/index.html), the first usage of `git add` was introduced with the sentence > We can tell Git to track a file using git add And after...
Would it make sense to update the section https://github.com/swcarpentry/git-novice/blame/0f775ae563a09163984e134b068d56928104ee29/_episodes/02-setup.md to something like: > Let's test and review the settings we made just now. Type `git config --global --edit` to open...
The section discussing using `git diff HEAD` states "which is the same as what you would get if you leave out HEAD (try it)" with no explanation as to WHY...
The end of [8 - Collaborating](http://swcarpentry.github.io/git-novice/08-collab/index.html) includes a "Basic Collaborative Workflow". A visual representation of this that connects the actions and commands to the learner's mental model (working, staging, local...
Hi, first of all thanks for the software carpentry git lesson. I think it is already great and I only have a minor remark/improvement. In the chapter https://swcarpentry.github.io/git-novice/05-history/index.html there is...
Proposal: I would like to propose to change the order of events when creating a conflict in lesson 9 – "Conflicts". Conflicts are more likely to occur when multiple people...
The git-novice workshop is really good, and I got to learn about git fairly sufficiently without prior experience in it. However, the lessons instruct the learner to edit texts as...
Hi! Please see https://github.com/carpentries/lesson-example/issues/234 for background on this suggestion. Cheers :-)
git status seems to me an important and useful enough command to be included in the lesson objectives.
