Publish targets output into a Tree Artifact (directory) instead of explicitly listing files. Therefore any runfiles that bazel would output would be output to publish.runfiles where they should be output to publish/net5.0/console.dll.runfiles, assuming that the end user wants to package up the publish directory.
We could have the builder manually create the runfiles by enumerating and copying them
The assumption is that we'd want to do a full copy of the runfiles since the publish executable would need to be functional on its own. It is possible there are usecases where this is not desireable
We could have bazel generate the runfiles to publish.runfiles and then add an extra action that merges somehow
Publish targets output into a Tree Artifact (directory) instead of explicitly listing files. Therefore any runfiles that bazel would output would be output to
publish.runfileswhere they should be output topublish/net5.0/console.dll.runfiles, assuming that the end user wants to package up the publish directory.publish.runfilesand then add an extra action that merges somehow