chore: cleanup changelog, update repo refs to pact-js-cli not pact-cli

.github/ISSUE_TEMPLATE/feature_request.md

@@ -24,10 +24,10 @@ Before making a feature request, I have:
 
 ### Feature description
 
-_Please describe what you would like Pact-js-core to do_
+_Please describe what you would like Pact-cli to do_
 
 ### Use case
 
 _What is the use case that motivates this feature request?_
 
-_Please describe *why* you would like Pact-js-core to have this feature._
+_Please describe *why* you would like Pact-cli to have this feature._

.github/pull_request_template.md

@@ -2,7 +2,7 @@ _Please read and then remove this section_
 
 Thank you for making a pull request!
 
-Pact-js-core is built and maintained by developers like you, and we appreciate contributions very much. You are awesome!
+Pact-cli is built and maintained by developers like you, and we appreciate contributions very much. You are awesome!
 
 Our changelog is automatically built from our commit history, using conventional changelog. This means we'd like to take care that:
 

README.md

@@ -407,7 +407,7 @@ messageFactory.createMessage();
 
 ### Enable Long Paths
 
-[Windows has a default path length limit of 260](https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation) causing issues with projects that are nested deep inside several directory and with how npm handles node_modules directory structures.  To fix this issue, please enable Windows Long Paths in the registry by running `regedit.exe`, find the key `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled` and change the value from `0` to `1`, then reboot your computer.  Pact should now work as it should, if not, please [raise an issue on github](https://github.com/pact-foundation/pact-js-core/issues).
+[Windows has a default path length limit of 260](https://docs.microsoft.com/en-us/windows/desktop/fileio/naming-a-file#maximum-path-length-limitation) causing issues with projects that are nested deep inside several directory and with how npm handles node_modules directory structures.  To fix this issue, please enable Windows Long Paths in the registry by running `regedit.exe`, find the key `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled` and change the value from `0` to `1`, then reboot your computer.  Pact should now work as it should, if not, please [raise an issue on github](https://github.com/pact-foundation/pact-cli/issues).
 
 ## Contributing
 

script/ci/release.sh

@@ -16,7 +16,7 @@ else
     git config user.name "${GITHUB_ACTOR}"
   fi
 fi
-REPO=${REPO:-pact-foundation/pact-js-core}
+REPO=${REPO:-pact-foundation/pact-js-cli}
 
 # It's easier to read the release notes
 # from the standard version tool before it runs

src/logger/crashMessage.ts

@@ -4,8 +4,8 @@ export const pactCrashMessage = (
 
 ${extraMessage}
 
-This is almost certainly a bug in pact-js-core. It would be great if you could
-open a bug report at: https://github.com/pact-foundation/pact-js-core/issues
+This is almost certainly a bug in pact-cli. It would be great if you could
+open a bug report at: https://github.com/pact-foundation/pact-cli/issues
 so that we can fix it.
 
 There is additional debugging information above. If you open a bug report, 

src/pact.ts

@@ -33,7 +33,7 @@ export class Pact {
       } catch {
         logger.warn(
           'WARNING: Windows Long Paths is not enabled and might cause Pact to crash if the path is too long. ' +
-            'To fix this issue, please consult https://github.com/pact-foundation/pact-js-core#enable-long-paths`'
+            'To fix this issue, please consult https://github.com/pact-foundation/pact-cli#enable-long-paths`'
         );
       }
     }