• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tarmolov / git-hooks-js / 174 / 1
99%
master: 98%

Build:
Build:
LAST BUILD BRANCH: use-relative-paths-in-hooks
DEFAULT BRANCH: master
Ran 26 Apr 2019 09:32PM UTC
Files 2
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

26 Apr 2019 09:31PM UTC coverage: 98.958% (+0.01%) from 98.947%
174.1

Pull #62

travis-ci

web-flow
Use relative path to git-hooks in installed hooks scripts

Before this patch, installing git-hooks would use absolute paths to
require `node_modules/git-hooks/lib/git-hooks`. This works most of
the time, but there are instances in which it does not. For example:

I do development on a host machine, but yarn install runs inside a
Docker container. In this case, the absolute path to `node_modules`
is different in the two environments. This means for the git-hooks
module to work as intended, I am only able to run Git commands from
inside of the container. I typically run Git commands from the host
machine, so this doesn't work for me.

More importantly, though, I see no reason to force everybody working
on my project to use Git in one environment or the other.

After this patch, installed git-hooks use relative paths to require
`node_modules/git-hooks/lib/git-hooks`.
Pull Request #62: Use relative path to git-hooks in installed hooks scripts

95 of 96 relevant lines covered (98.96%)

33.29 hits per line

Source Files on job 174.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 170
  • Travis Job 174.1
  • 66f384e5 on github
  • Prev Job for on use-relative-paths-in-hooks (#172.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc