Publishers should emit assets to a separate directory
Open
area-deployment
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
Currently, all `PublishingCallbacks` emit their assets to the output path. Unless the publisher emits to a subdirectory itself, this can make for confusing outputs. For example, Azure and Docker Compose publishers in one:
We should consider separating each output into a directory keyed by the environment name or something...
Contributor guide
Assessment
This issue has not been assessed yet.