eficode-academy / git-katas Goto Github PK

There is generally an issue with moving people in to the exercise folder.
If we are using ./setup.sh we are not moving people in there. We are with . setup.sh

We should have different learning paths through the gitkatas.

A noob could start with basic-staging -> basic-branching -> something something

while we could also have a "superuser" path that does more advanced stuff
An admin path could also be useful

I don't know quite how to do this, but it is an obvious omission that we should fill out.

We saw a student using zsh where the for-loop
syntax of {1..10} did not work.

Is the goal of this kata to make a checkout to the kata3-detached-head branch?

Should possibly be broken down into the separate exercises when started.
Multiple places there are "What do you see?" questions. Some of these feels like trick questions. Make it more obvious what the user is looking for.

Looking at the text, and the branching, it is not clear where master should be rebased to.
Isn't it the case that it should be kata2-squashing that were at master's place. Else rename master, since you never rewrite public history, and users sees master as something public.

The current way may cause confusion and trying to execute a run setup.sh command.

Make it more explicit in the READMEs for example like this:

Run the setup script:

./setup.sh

PS: Does this work in Git Bash without the .sh files being executable?

Create file1.txt before mentioning txt files.

examines the following commands in regards to a branch

1. git branch and -a
2. git checkout and -b
3. git diff

Along with the shorthand notations HEAD ^ ~

Examples:

There should be two branches, both pointing to the same commit.

1. List the branches
2. Go to the other branch, that points to the same commit
3. git status
4. Make a commit
5. git status
6. git log --all --decorate --graph --oneline
7. back to the first branch
8. make commit
9. git status
10. git log --all --decorate --graph --oneline

Talk about merging, but wait to show it to another kata.

See #11
which should be applied to all places where the alias is mentioned:

$ grep -nrI "alias\.lol" *

The opening descriptions of basic-branching and 3-way-merge are identical.
Give 3-way-merge a unique description.

It would be really nice if the user could just write ./amidone.sh and then get a true/false reply.

This one is a bit tricky. It does not create an exercise dir and git init that. But it should.
But then setup.sh doesn't quite works, because after one commit, we cannot checkout HEAD~1.

Right now the basic-branching require us to go all the way to slide 44 because is also has merging in it.
I suggest we make a basic-branching and a basic-merging in order to accommodate an early entry of a lab (slide 24)

The ignore kata is described as basic but launches straight into the advanced use case where you ignored a filetype that is already added, and doesn't even provide explanation as to what is expected.

I think the basic ignore kata should be much more basic.