Nick Merwin

+1 @Aupajo's method worked on fresh install just now.

@wkirby could you upload your lcov file so I can see what's going on? Thank you!

Hi @geoff-reid, we now factor branches into the overall coverage %, so that 85% is: `(1686 covered branches + 6413 covered lines) / (2284 branches + 7186 relevant lines)`

@wkirby we're only passing along the `BRDA:..` lines from the lcov.info, and I see 78 in your's but no indication of which should be ignored -- do you know where...

@wkirby ok I see, so it looks like we'll need to add a `BRH` override parameter to the API. It's unfortunate that it won't be reflected in the source file...

@selfcontained we've added a toggle for this in the repo settings if you'd prefer to disable it: 

@vitaly-t that's a good point, while we wanted existing repo owners to be immediately aware of uncovered branches, it should be opt-in so as not to disrupt automated build workflows....

Hi @wheresrhys this seems to be a CircleCI specific issue -- when running on Travis it checks out the tagged branch and writes the file `.git/refs/heads/` . Could you re-run...

hei @piotr-s-brainhub and @rook2pawn, could you please run your build with `coveralls --verbose` and link me to the output?

Hi @daleharvey and @BanzaiMan, in [coveralls-ruby](https://github.com/lemurheavy/coveralls-ruby) we get the git info using `git log -1`, e.g.: ``` ruby message = `git log -1 --pretty=format:'%ce'` ``` https://github.com/lemurheavy/coveralls-ruby/blob/master/lib/coveralls/configuration.rb#L138 Do you think changing...