Fix fatal error if not in git dir

[cy4n]

following command throws an error in git 2.13.0 macosx:

git config --local --get oh-my-git.enabled
fatal: BUG: setup_git_env called without repository
(appears in base.sh:49)

this fix pipes the "fatal..." output to /dev/null (as you already do in every other git command :-)

[UFOMelkor]

Same bug occurs on openSUSE with git 2.13.0.

[cy4n]

looks like its not an actual bug, but git added some error messages when you use git in non-git folders
technically this is not a bug in ohmygit either, but you probably want to hide the message :-)

[djbclark]

Thanks I was seeing this too, linuxbrew after update to 2.13.0. Please merge :-)

#110 is a dupe of this bug.

[borja]

Tested locally.. Thanks for the fix, @cy4n . LGTM.
Please merge 😄

[huxi]

Message changed from fatal: BUG: setup_git_env called without repository (2.13.1) to fatal: --local can only be used inside a git repository (2.13.2).

[huxi]

This should really remove --local instead of piping the error to /dev/null as @sw0x2A said in a #110 comment.

[cy4n]

actually skipping --local would also allow to globally disable oh-my-git by adding

[oh-my-git]
enabled=false

to the global ~/.gitconfig
and only enable it on repos you actually want to use it by adding

[oh-my-git]
enabled=true 

in the local .git/config
this would also prevent the local exploit in #104.
or at least you actually see the branch name in the config when you add the enable=false line

[cy4n]

approved @huxi ;)

[andrewkew-aft]

When will this PR be merged into master? I would rather take the changes from master than be running a side branch.

[cy4n]

github says that @arialdomartini is still active,) ask him.
this repo has had its last change over a year ago.

[andrewkew-aft]

Cheers @cy4n I have pinged him, hopefully we can get this approved and merged.

[snowblink]

Any news on this @arialdomartini ?

[MindRave]

Hello! Are there any news on this? @arialdomartini

[arialdomartini]

@cy4n, @UFOMelkor, @djbclark, @borja, @huxi, @andrewkew-aft, @snowblink, @MindRave

shame on me. I've been neglecting this repo for more than 1 year already. I've got a bunch of issues to fix and pull requests to merge. Time to get up and work.
Thank you for your job!

[cy4n]

@arialdomartini before you merge all this PRs, maybe checkout my or @compholios fork, because we have picked some of the PRs and received PRs on top of them that are not necessarily in your upstream repo

[cy4n]

anyway welcome back

[arialdomartini]

Hi @cy4n.
Sure, thank you!
I think we have 2 options, here. Either I could just merge the last commit of your fork, review all the job you did during the last months, and start over from there; or I could start from the PRs to this repo, always comparing the result with the commits in your repo. In both cases, I think it would be beneficial to reduce as much as possible the distance between this repo and your fork.

I think I will go with the former. Keep in touch, please, I'm going to ask your opinion on some PRs...

Grazie mille!