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.

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

Add testing for github workflows #22

Open
loreanvictor opened this issue Sep 15, 2020 · 2 comments
Open

Add testing for github workflows #22

loreanvictor opened this issue Sep 15, 2020 · 2 comments

Comments

@loreanvictor
Copy link
Contributor

Add some testing mechanism for github workflows and test (and debug) npm-publish workflow. Perhaps this tool helps?

@TysonMN
Copy link
Contributor

TysonMN commented Sep 15, 2020

I figured out how to test the npm-publish GitHub workflow.

In short, I

  1. created my GitHub fork of the current repo,
  2. made test-specific changes in this commit,
  3. set the version to 0.1.17 in this commit with message Release 0.1.17, and
  4. pushed both commits to master in my GitHub fork.

Then pascalgn/[email protected] did everything it was supposed to (while logging about it). Now the published version 0.1.17 is available here.

So, I am now confident in the correctness of the GitHub workflow. Here are the steps needed to use this GitHub workflow "for real".

One time

  1. Complete PR Adds npm install steps to publish workflow #23.
  2. Create a new GitHub secret with the name NPM_AUTH_TOKEN and with a value of a personal authentication token for your account on npmjs.com.

Every time

  1. Change the value of the version key in package.json to x.y.z with desired values of x, y, and z.
  2. Commit that change to master with message Release x.y.z using the same values of x, y, and z.
  3. Push that commit to the current repository (if that commit was created in a fork of this repository).

@TysonMN
Copy link
Contributor

TysonMN commented Sep 15, 2020

I suppose one more thing you could do is download this version 0.1.17 that I published and manually inspect it to see if it as you expect it to be.

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

No branches or pull requests

2 participants