Zarf publishes empty packages to private repo when package name is not specified about zarf HOT 2 OPEN

This may be some confusion in what publish does does for different source types. When you pass a directory as the argument you are pushing up a skeleton package which does not contain any of the package resources.

Skeleton packages have not been run through the zarf package create process yet, and thus do not have any remote resources included (no images, repos, or remote manifests and files) thereby retaining any create-time package configuration templates as they were defined in the original zarf.yaml (i.e. untemplated).

https://docs.zarf.dev/faq/#what-is-a-skeleton-zarf-package

I do understand that it can be confusing as the behavior depends on the input to the command. While the CLI output gives some indication that you have created a skeleton package I think that it could be a bit more clear.

from zarf.

Would it a good idea to add a flag to allow zarf publish to publish a zarf packages found in a directory when a directory is passed as the argument? If not I see no reason not to close this issue. Thank you for the response.

from zarf.