Skip to content

Update working-with-the-npm-registry.md#31653

Closed
debjeet214 wants to merge 1 commit intogithub:mainfrom
debjeet214:patch-1
Closed

Update working-with-the-npm-registry.md#31653
debjeet214 wants to merge 1 commit intogithub:mainfrom
debjeet214:patch-1

Conversation

@debjeet214
Copy link
Copy Markdown

@debjeet214 debjeet214 commented Feb 15, 2024

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

@welcome
Copy link
Copy Markdown

welcome Bot commented Feb 15, 2024

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Feb 15, 2024
@debjeet214
Copy link
Copy Markdown
Author

see this change

@github-actions
Copy link
Copy Markdown
Contributor

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md fpt
ghec
ghes@ 3.12 3.11 3.10 3.9 3.8
fpt
ghec
ghes@ 3.12 3.11 3.10 3.9 3.8

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836
Copy link
Copy Markdown
Contributor

@debjeet214 Thanks for opening a PR! 👍 Please fill out the pull request template in the top comment in this pull request in its entirety, then we'll get this up for review!

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team packages This issue or pull request should be reviewed by the docs packages team more-information-needed More information is needed to complete review and removed triage Do not begin working on this issue until triaged by the team labels Feb 15, 2024
@debjeet214 debjeet214 closed this by deleting the head repository Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content This issue or pull request belongs to the Docs Content team more-information-needed More information is needed to complete review packages This issue or pull request should be reviewed by the docs packages team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants