Skip to content

Conversation

@rakshith-ravi
Copy link
Member

No description provided.

@rakshith-ravi
Copy link
Member Author

@thebongy I've kept this as a base for you to work on top of. Feel free to change my PR's contents.

Also, idk if your version-check action supports JSON files for package.json yet

@thebongy
Copy link
Contributor

thebongy commented Apr 26, 2020 via email

@thebongy
Copy link
Contributor

thebongy commented May 1, 2020

Closed in favor of #8

@thebongy thebongy closed this May 1, 2020
@rakshith-ravi
Copy link
Member Author

#8 targets feature/npm-publish branch. Once that gets merged, this PR will be updated, which targets master. We can merge this as soon as that gets merged

@rakshith-ravi rakshith-ravi reopened this May 1, 2020
@rakshith-ravi
Copy link
Member Author

@thebongy I've added NPM_TOKEN to the secrets. Feel free to merge this once this is done. Make sure master, staging and develop branches are setup as well, along with the appropriate branch protection.

@thebongy thebongy merged commit 8c9a96c into master May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add github workflows for npm publish and tagging

4 participants