From ee5fb9108c250bedb274d6f611451ca04f8a7bae Mon Sep 17 00:00:00 2001 From: Jacob Hummer Date: Tue, 7 May 2024 20:13:06 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index eda0e1a..095587b 100644 --- a/README.md +++ b/README.md @@ -82,4 +82,4 @@ This can be useful if you need to resolve the path to a specific binary (`cat.ex ![Node.js](https://img.shields.io/static/v1?style=for-the-badge&message=Node.js&color=339933&logo=Node.js&logoColor=FFFFFF&label=) ![GitHub Actions](https://img.shields.io/static/v1?style=for-the-badge&message=GitHub+Actions&color=2088FF&logo=GitHub+Actions&logoColor=FFFFFF&label=) -You'll need a Windows computer to test this package locally. You can run `npm run build` to make sure everything looks good locally. `npm run generate` will check for a new Git for Windows PortableGit release and download it if it exists. There's a CI script that automatically runs `npm run generate` every so often and will open Pull Requests for updates. Merging these PRs to `main` **does not automatically create a new release** -- that must be done manually. Each new release automagically publishes to npm. +You'll need a Windows computer to test this package locally. You can run `npm run build` to make sure everything looks good locally. `npm run generate` will check for a new Git for Windows PortableGit release and download it if it exists. Make sure you do this manually on each new Git for Windows release. You can subscribe to releases on the [git-for-windows/git](https://github.com/git-for-windows/git) repository.