From 8f0809ffef999a91ae9c6cf69ec6b6fbc8cbd66c Mon Sep 17 00:00:00 2001
From: Alexander Lisianoi <all3fox@gmail.com>
Date: Thu, 1 Feb 2018 21:39:34 +0100
Subject: [PATCH] Harden getProjectPath() to deal with different PATHs

PATH could contain both relative and absolute values, so just add an
extra path.resolve() call.

Refs: https://github.com/jzaefferer/commitplease/issues/106
---
 index.js | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/index.js b/index.js
index c2f34cc..a104a3f 100644
--- a/index.js
+++ b/index.js
@@ -30,6 +30,9 @@ function sliceEnvPath (suffix) {
 // commitplease. Previously, process.cwd() made the job easy but its
 // output changed with node v8.1.2 (at least compared to 7.10.0)
 function getProjectPath () {
+  // Rely on npm to inject some path into PATH; However, the injected
+  // path can both be relative or absolute, so add extra path.resolve()
+
   // During npm install, npm will inject a path that ends with
   // commitplease/node_modules/.bin into process.env.PATH
   var p = sliceEnvPath(
@@ -37,7 +40,7 @@ function getProjectPath () {
   )
 
   if (p !== undefined) {
-    return p
+    return path.resolve(p)
   }
 
   // During npm run, npm will inject a path that ends with
@@ -45,14 +48,14 @@ function getProjectPath () {
   p = sliceEnvPath(path.join('node_modules', '.bin'))
 
   if (p !== undefined) {
-    return p
+    return path.resolve(p)
   }
 
   // During git commit there will be no process.env.PATH modifications
   // So, assume we are being run by git which will set process.cwd()
   // to the root of the project as described in the manual:
   // https://git-scm.com/docs/githooks/2.9.0
-  return process.cwd()
+  return path.resolve(process.cwd())
 }
 
 function getOptions () {