Skip to content

Simplify npm publish step in workflow#32

Open
gracepark wants to merge 1 commit into
github:mainfrom
gracepark:patch-1
Open

Simplify npm publish step in workflow#32
gracepark wants to merge 1 commit into
github:mainfrom
gracepark:patch-1

Conversation

@gracepark
Copy link
Copy Markdown

Part of: https://github.com/github/web-systems/issues/4309

Removed npm whoami command from publish step.

Removed npm whoami command from publish step.
Copilot AI review requested due to automatic review settings May 8, 2026 20:31
@gracepark gracepark requested a review from a team as a code owner May 8, 2026 20:31
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR aims to simplify the GitHub Actions release workflow used to publish the package to npm.

Changes:

  • Removes npm whoami from the publish step.
  • Modifies the npm publish step invocation (and currently also removes the auth env block for the step).
Show a summary per file
File Description
.github/workflows/publish.yml Simplifies the npm publish step in the release workflow (but also drops the publish auth env configuration).

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 2

Comment thread .github/workflows/publish.yml
Comment thread .github/workflows/publish.yml
@gracepark
Copy link
Copy Markdown
Author

Hi @maraisr! Thanks for the review! I noticed that I'm running into this error:

Code scanning is waiting for results from CodeQL for the commits e3baae5 or 4ceb530.

I'm unable to see the settings on the repo since (I don't have permissions). Would you be able to check this for me? I think you can disable the CodeQL-block repo custom property to immediately disable CodeQL blocking this PR, but I'm not sure if that's what your team would want.

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