Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: update readme with publishing instructions #20

Merged
merged 1 commit into from
Apr 7, 2022
Merged

docs: update readme with publishing instructions #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,3 +73,16 @@ As opposed to the `pull_request` event trigger which can derrive `commit_hash`,
When the action completes, you should see an annotation that looks like this:

![workflow dispatch annotation](assets/workflow_dispatch_annotation.png)

## Development

### Releasing new versions to GitHub Marketplace

It's easiest to just use `npm` to manage the versioning:

1. `npm version [major, minor, patch]`_\*_
2. `git push origin head --tags`

_note: this will update the version field in `package.json`, run a build & commit those changes_

Read more about [publishing actions in GitHub Marketplace](https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace).