Rebase is used in merging two or more commits into one. Per experience, you can only rebase to an older commit.
Say, in these commits
1~$ git log -2 --pretty=oneline 2a0dd6b55000399c5f8b5f0f55286e167725e51c2 (HEAD -> v0.2.x_wip, origin/v0.2.x_wip) docktie_cli getx: Tested working implementation for #17. …
Submodules is quite a pain to manage. To make it easy, just use this command:
1git clone --recursive <repo_full_path> Failure to use --recursive would mean using a lot of commands later.
See detailed git submodules commands in https://www.vogella.com/tutorials/GitSubmodules/article.html
Get the commit-hash (e.g. of last commit)
1git log -1 Show the files changed only in commit
1git show --stat <commit-hash> See details in https://stackoverflow.com/questions/424071/how-to-list-all-the-files-in-a-commit
When you see error such as this
1bash-4.1$ git checkout Brick_Release_2018-06-19 2error: pathspec 'Brick_Release_2018-06-19' did not match any file(s) known to git. 'git fetch' first and retry to checkout. If it still fails, ensure you're using the correct branch name.