Harry Dobrev

`class_exists` checks are also quite common and would probably also suffer from the same issue.

@surfer190 Could you please modify an existing file, stage it and see if this command gives you any output: ``` git diff-index --cached --name-only --diff-filter=ACMR HEAD ``` The `M` in...

You don't need comments like that in your commits. If I really, really do want to commit comments like that I would use the `--no-verifiy` option flag.

#42 should fix the problem, but the `2.1.2`version is not yet available in RubyGems.org: http://rubygems.org/gems/tumblr-rb/versions

In addition `tumblr edit` is not working similarly to `tumblr post`. When I have a file which I want to post I can just `tumblr post filename.md`, but if I...

@adanilowski I think this is quite a drastic change compared to how the lock file currently works and is a breaking change. My suggestion is around the current implementation and...

I suppose we need to detect just the following: - is there a merge conflict - is the merge conflict just in the hash If it is, we just need...

> if we target a specific version number, then newer commits should not matter, right? unless there is a force-push. Even without a force push, git allows deleting a tag...

I've been using the [Composer Git merge driver](https://github.com/balbuf/composer-git-merge-driver) for some time and it works well for simple cases. It however causes more confusion with more complex cases and it can...

> This one might be hard to implement, because composer loads the composer.json file quite early (as it contains some config stuff), and would fail there in case of an...