Open
Description
When you have a dependency configured like "name @ {root:uri}/vendor/name.1.zip" the requirements.txt file will have the full path like file:///home/user/code/project/vendor/name.1.zip. Everything works when another person runs it on another machine, but the requirements file will have been updated to have the path on their machine, which causes git churn.
Can the requirements.txt file store the entry with a relative path or keeping the {root:uri} present?
Metadata
Metadata
Assignees
Labels
No labels