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

Use backtick to format references to file names in working-with-the-npm-registry #35765

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

yolocat-dev
Copy link

@yolocat-dev yolocat-dev commented Dec 24, 2024

Why:

Closes:

#35763
#35762

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

.npmrc -> .npmrc
package.json -> package.json

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing.

…blishing-a-package-using-a-local-npmrc-file`
…m-registry#publishing-a-package-using-publishconfig-in-the-packagejson-file`
Copy link

welcome bot commented Dec 24, 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 Dec 24, 2024
Copy link
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.15 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

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

@yolocat-dev yolocat-dev changed the title Backtick patch Use backtick to format references to file names in working-with-the-npm-registry Dec 24, 2024
@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 ready to merge This pull request is ready to merge and removed triage Do not begin working on this issue until triaged by the team labels Dec 26, 2024
@nguyenalex836
Copy link
Contributor

@yolocat-dev Thank you so much for opening a PR with this fix! Your changes look great ✨ We are currently in a repo freeze, but we'll get this merged as soon as the freeze ends on Jan 6th 💛

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 packages This issue or pull request should be reviewed by the docs packages team ready to merge This pull request is ready to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants