From e9938d0dd18041e60f7dfdd7f4e89b630447fb79 Mon Sep 17 00:00:00 2001 From: Alvaro Jose Date: Mon, 14 Aug 2023 10:31:59 +0200 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c8ad913..d75198c 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ GitHub Action for automated npm publishing. -This Action publishes a package to npm. It is meant to be used on every successful merge to master but +This Action publishes a package to npm. It is meant to be used on every successful merge to main but you'll need to configure that workflow yourself. You can look to the [`.github/workflows/push.yml`](./.github/workflows/release.yml) file in this project as an example. @@ -40,7 +40,7 @@ You can configure some aspects of merge-release action by passing some environme `merge-release` will use `npm publish` unless you've defined a `publish` script in your `package.json`. ```yaml -- uses: Github-Actions-Community/merge-release@master +- uses: Github-Actions-Community/merge-release@main env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} NPM_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}