Skip to content

fix: update npm-dev.yaml #4781

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

Merged
merged 1 commit into from
Jan 22, 2022
Merged

fix: update npm-dev.yaml #4781

merged 1 commit into from
Jan 22, 2022

Conversation

jsjoeio
Copy link
Contributor

@jsjoeio jsjoeio commented Jan 21, 2022

I didn't think it through in my previous PR but since this workflow only runs on a merge into main, there is no PR number. So instead, we use the word "beta" and then we also have to grab a different SHA since there is no PR SHA.

Prevents this from happening again: https://www.npmjs.com/package/code-server/v/4.0.1--
https://github.com/coder/code-server/runs/4903294989?check_suite_focus=true#step:3:16

Fixes N/A

@jsjoeio jsjoeio self-assigned this Jan 21, 2022
@jsjoeio jsjoeio requested a review from a team January 21, 2022 23:44
@jsjoeio jsjoeio temporarily deployed to CI January 21, 2022 23:44 Inactive
PR_NUMBER_AND_COMMIT_SHA: ${{ github.event.number }}-${{ github.event.pull_request.head.sha }}
# Since this only runs on a merge into main, we can't use github.event.number
# so we instead use the word "beta" and the PR merge commit SHA
PR_NUMBER_AND_COMMIT_SHA: beta-${{ github.sha }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't love using "beta" where you would expect a PR_NUMBER but this was the least invasive change I could think of. I didn't want to have to add another environment variable and make this more complicated than it needs to be.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But then again, we could always change this to NPM_VERSION but I don't know if that will make it more complicated. Open to ideas. Just wanted to open a fix quickly.

Copy link
Member

@code-asher code-asher Jan 26, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My bad, I reviewed too quickly and missed this comment I think 😛

In case this is still relevant, I think it is a valid concern and NPM_VERSION would describe what this variable is for perfectly.

@codecov
Copy link

codecov bot commented Jan 21, 2022

Codecov Report

Merging #4781 (95938d6) into main (a2f5301) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #4781   +/-   ##
=======================================
  Coverage   69.18%   69.18%           
=======================================
  Files          29       29           
  Lines        1652     1652           
  Branches      363      363           
=======================================
  Hits         1143     1143           
  Misses        432      432           
  Partials       77       77           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a2f5301...95938d6. Read the comment docs.

@github-actions
Copy link

✨ Coder.com for PR #4781 deployed! It will be updated on every commit.

@im-coder-lg
Copy link
Contributor

@jsjoeio jsjoeio merged commit 8816ab9 into main Jan 22, 2022
@jsjoeio jsjoeio deleted the jsjoeio-patch-2 branch January 22, 2022 15:48
@jsjoeio
Copy link
Contributor Author

jsjoeio commented Jan 22, 2022

@im-coder-lg no, different fix. That should also be fixed though!

TinLe pushed a commit to TinLe/code-server that referenced this pull request Apr 23, 2022
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.

3 participants