eficode-academy / git-katas Goto Github PK
View Code? Open in Web Editor NEWA set of exercises for deliberate Git Practice
License: MIT License
A set of exercises for deliberate Git Practice
License: MIT License
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.
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
Create file1.txt before mentioning txt files.
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?
examines the following commands in regards to a branch
git branch
and -a
git checkout
and -b
git diff
Along with the shorthand notations HEAD ^ ~
Examples:
There should be two branches, both pointing to the same commit.
Talk about merging, but wait to show it to another kata.
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
.
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
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)
See #11
which should be applied to all places where the alias is mentioned:
$ grep -nrI "alias\.lol" *
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.
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.
Is the goal of this kata to make a checkout to the kata3-detached-head branch?
The opening descriptions of basic-branching
and 3-way-merge
are identical.
Give 3-way-merge
a unique description.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.