level 37: a branch called "if this commit gets pushed you have lost the level" should be committed

[noamraph]

No description provided.

[Gazler]

@noamraph what command would you use to get into that state?

[noamraph]

@Gazler It's just the level - I think that it's confusing that the commit with that label should be pushed.

[Gazler]

@noamraph The goal of the level is to push the branch without the commit called "if this commit gets pushed you have lost the level"

That commit exists on master and other_branch but not on test_branch which is the one to be pushed.

[AbuDarian]

I also find this one very confusing. I looked in to pushing a singel commit, pushing a single branch and every other possibillity I can think of. But I always seem to get "The solution isn't quite right"....any advice?

[Gazler]

@AbuDarian the point is to commit a different branch to the repository. You can see the solution at

githug/spec/githug_spec.rb

Line 220 in 3b0cccd

`git push origin test_branch`

[AbuDarian]

@Gazler :Your solution is the first one I tried. But it seems to be a different kind of problem.

[Gazler]

I see the problem - it is using wc which is a Unix command on windows. An
issue was raised recently at #186
On 9 Feb 2015 08:05, "Ala Shakrah" notifications@github.com wrote:

@Gazler https://github.com/Gazler :Your solution is the first one I
tried. But it seems to be a different kind of problem.

[image: image]
https://cloud.githubusercontent.com/assets/8581487/6102598/957b0114-b039-11e4-921c-883821ff8175.png

—
Reply to this email directly or view it on GitHub
#164 (comment).

[AbuDarian]

My selfconfidence was shot for about 3 days....:-) its good to know the problem lay elseware

[Gazler]

@AbuDarian sorry about that! I'll continue communication on the other issue.