Somewhere in the workspace I think I must have introduced another branch and called it the same name as the one I am trying to commit a change to. How can I find it? Is my only option to delete the workspace and just start the tutorial over again?
olddognewtrix123:~/workspace/kloneklone/patchwork (add-olddognewtrix123) $ cd contributors
olddognewtrix123:~/workspace/kloneklone/patchwork/contributors (add-olddognewtrix123) $ git status
On branch add-olddognewtrix123
Untracked files:
(use "git add <file>..." to include in what will be committed)
add-olddognewtrix123.txt
nothing added to commit but untracked files present (use "git add" to track)
olddognewtrix123:~/workspace/kloneklone/patchwork/contributors (add-olddognewtrix123) $ git add add- olddognewtrix123.txt
olddognewtrix123:~/workspace/kloneklone/patchwork/contributors (add-olddognewtrix123) $ git commit -m "hope this works!"
[add-olddognewtrix123 265d785] hope this works!
1 file changed, 1 insertion(+)
create mode 100644 contributors/add-olddognewtrix123.txt
olddognewtrix123:~/workspace/kloneklone/patchwork/contributors (add-olddognewtrix123) $ git-it verify
Verifying "BRANCHES AREN'T JUST FOR BIRDS"...
ACTUAL EXPECTED
------ --------
"Found branch as expected!" "Found branch as expected!"
"{ [Error: Command failed: /bin/sh -c git reflog show origin/add-olddognewtrix123" != "Changes have been pushed!"
"fatal: ambiguous argument 'origin/add-olddognewtrix123': unknown revision or path not in the working tree." != "File in contributors folder!"
"Use '--' to separate paths from revisions, like this:" != ""
"'git <command> [<revision>...] -- [<file>...]'" != null
"]" != null
" killed: false," != null
" code: 128," != null
" signal: null," != null
" cmd: '/bin/sh -c git reflog show origin/add-olddognewtrix123' }" != null
"" != null
# FAIL
Your solution to BRANCHES AREN'T JUST FOR BIRDS didn't match the expected output.
Try again!