This repository was archived by the owner on Jun 11, 2020. It is now read-only.
Specify directory within DefinitelyTyped repo in repository object #578
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Currently, it's hard for automated tools to find the relevant package within the
DefinitelyTypedmonorepo when constructing commits diffs etc.I worked with the npm team to add a standard for declaring the directory within a repository that a package lives in. The accepted RFC is here, and the new guidance was accepted into npm's docs here.
This PR adds the recommended
directoryattribute to the repository specification for each package. It will allow tools like Dependabot to show only the commits that are relevant to a particular packages when creating PRs.