Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
jcbhmr authored May 8, 2024
1 parent 2c2179d commit ee5fb91
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

0 comments on commit ee5fb91

Please sign in to comment.