Skip to content

Commit 89b41e6

Browse files
authored
Fix typos in README.md (#384)
1 parent c62ef97 commit 89b41e6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This action for [Changesets](https://github.com/atlassian/changesets) creates a
1616

1717
### Outputs
1818

19-
- published - A boolean value to indicate whether a publishing is happened or not
19+
- published - A boolean value to indicate whether a publishing has happened or not
2020
- publishedPackages - A JSON array to present the published packages. The format is `[{"name": "@xx/xx", "version": "1.2.0"}, {"name": "@xx/xy", "version": "0.8.9"}]`
2121

2222
### Example workflow:
@@ -124,7 +124,7 @@ For example, you can add a step before running the Changesets GitHub Action:
124124

125125
#### Custom Publishing
126126

127-
If you want to hook into when publishing should occur but have your own publishing functionality you can utilize the `hasChangesets` output.
127+
If you want to hook into when publishing should occur but have your own publishing functionality, you can utilize the `hasChangesets` output.
128128

129129
Note that you might need to account for things already being published in your script because a commit without any new changesets can always land on your base branch after a successful publish. In such a case you need to figure out on your own how to skip over the actual publishing logic or handle errors gracefully as most package registries won't allow you to publish over already published version.
130130

0 commit comments

Comments
 (0)