Hello, I have been working for years with junior developers and I find that many of them struggle to get out of some "delicate situations".
Example "detached head", "wrong rebase", "for some reason I see duplicate commits" and so on.
To help my colleagues I came up with a list of git uses cases that can be tested in a sort of interactive playground using a shell script that will set-up the use case and then we can go ahead and try to solve the problem.
The main advantage here is that all use cases are reproducible and that by looking at the shell script we can see how we got in the mess in the first place.
Everything is written in posix shell and should work on linux, macos and windows (with git bash).
Any comments, feedback and contributions are very welcome !
To help my colleagues I came up with a list of git uses cases that can be tested in a sort of interactive playground using a shell script that will set-up the use case and then we can go ahead and try to solve the problem.
The main advantage here is that all use cases are reproducible and that by looking at the shell script we can see how we got in the mess in the first place.
Everything is written in posix shell and should work on linux, macos and windows (with git bash).
Any comments, feedback and contributions are very welcome !
PS: This is somewhat inspired by https://ohshitgit.com/