Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Closed
Leslie-T-art wants to merge 1 commit into from
Closed

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

Leslie-T-art wants to merge 1 commit into from

Conversation

@Leslie-T-art
Copy link

@Leslie-T-art Leslie-T-art commented Jan 10, 2024 •
edited
Loading

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

welcome bot commented Jan 10, 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 Jan 10, 2024
@github-actions
Copy link
Contributor

github-actions bot commented Jan 10, 2024

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.11 3.10 3.9 3.8
fpt
ghec
ghes@ 3.11 3.10 3.9 3.8

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

@nguyenalex836
Copy link
Contributor

nguyenalex836 commented Jan 10, 2024

@Leslie-T-art Thanks for opening a PR ✨  Please fill out the pull request template in its entirety in the top comment in this pull request, 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 Jan 10, 2024
@github-actions github-actions bot added the stale There is no recent activity on this issue or pull request label Jan 17, 2024
@github-actions
Copy link
Contributor

github-actions bot commented Jan 17, 2024

This PR has been automatically closed because there has been no response to to our request for more information from the original author. Please reach out if you have the information we requested, or open a new issue to describing your changes. Then we can begin the review process.

@github-actions github-actions bot closed this Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

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 stale There is no recent activity on this issue or pull request

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Leslie-T-art @nguyenalex836