Skip to content

Commit b35b4ec

Browse files
committed
readme minor upd
1 parent 56d79c8 commit b35b4ec

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -145,7 +145,7 @@ If you publish your package to npm only, and don't want to publish to GitHub Pac
145145

146146
Now everything is set. The example package has automated tests and upload (publishing) already set up with GitHub Actions:
147147

148-
- Every time you `git push` your `master` or `main` branch, the package is automatically tested against the desired OS and Node.js versions with GitHub Actions.
148+
- Every time you `git push` or a pull request is submitted on your `master` or `main` branch, the package is automatically tested against the desired OS and Node.js versions with GitHub Actions.
149149
- Every time a new release (either the initial version or an updated version) is created, the latest version of the package is automatically published to npm and/or GitHub Packages registry with GitHub Actions.
150150

151151
Apparently, you have to change the version number in order to publish a new version to the registries. You can unpublish a version or the whole package but can never re-publish the same version under the same name.

0 commit comments

Comments
 (0)