Peg revisions and deploys trees, but uses individual files as entry points to identify trees. This can cause a problem if multiple entry points are found within a single directory because only one file can be listed in the tree's index for one revision (multiple entry points in one directory are therefore illegal).
In this scenario peg currently attempts to treat each entry as an independent tree, this fails when attempting to create duplicate deploy tags and does not revert the broken tags.
Peg should detect and warn users when multiple illegal entry points within a single directory are detected and disallow deployments on offending trees until they are fixed.
Peg revisions and deploys trees, but uses individual files as entry points to identify trees. This can cause a problem if multiple entry points are found within a single directory because only one file can be listed in the tree's index for one revision (multiple entry points in one directory are therefore illegal).
In this scenario peg currently attempts to treat each entry as an independent tree, this fails when attempting to create duplicate deploy tags and does not revert the broken tags.
Peg should detect and warn users when multiple illegal entry points within a single directory are detected and disallow deployments on offending trees until they are fixed.