Document --licensefile-to-license-mappings with explicit path resolution behavior#354
Merged
sensslen merged 2 commits intoDec 2, 2025
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
Co-authored-by: sensslen <3428860+sensslen@users.noreply.github.com>
|
Copilot
AI
changed the title
[WIP] Update documentation to include command line argument details
Document --licensefile-to-license-mappings with explicit path resolution behavior
Dec 2, 2025
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
--licensefile-to-license-mappingscommand line option lacked documentation. Users needed explicit guidance on path resolution semantics.Changes
Added
docs/licensefile-mappings-json.md: Documents JSON format and path resolution behavior. License file paths are resolved relative to the JSON file's directory, not the working directory.Updated README.md:
Example
Given a JSON file at
/project/config/license-mappings.json:{ "licenses/MIT.txt": "MIT", "../external/Apache.txt": "Apache-2.0" }Paths resolve to:
licenses/MIT.txt→/project/config/licenses/MIT.txt../external/Apache.txt→/project/external/Apache.txtOriginal prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.