Update README.md

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. There are some CI automation scripts to auto-release on new Git for Windows releases. It's all automated! 🤖 Check out [the gh-release-createworkflow ](./.github/workflows/gh-release-create.yml) to see how it works.
+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.