Clarify vsts-npm-auth only required when adding new packages #8850
+12
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CONTRIBUTING.md incorrectly implied that
vsts-npm-authauthentication was required for initial setup. Authentication is only needed when adding new packages to the Azure DevOps feeds, not for installing existing dependencies.Changes:
vsts-npm-authfrom initial setup steps, added note clarifying it's only needed when adding new packagesThis allows new contributors to build the project without Azure DevOps authentication, reducing friction in the onboarding process.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.