Right now, in order to get a README and LICENSE to be pushed alongside a module, users need to symlink these files into their modules. This can be inconvenient.
With v2 modules, the buf.yaml configuration is designed to be at the top-level of a repository, alongside many of these common files. If a module does not have a README/buf.md and/or LICENSE explicitly defined and/or symlinked to the module root, should we support pushing the top-level files as a default?
I am proposing this for v2buf.yaml workspaces only.
Feature
Right now, in order to get a
README
andLICENSE
to be pushed alongside a module, users need to symlink these files into their modules. This can be inconvenient. Withv2
modules, thebuf.yaml
configuration is designed to be at the top-level of a repository, alongside many of these common files. If a module does not have aREADME
/buf.md
and/orLICENSE
explicitly defined and/or symlinked to the module root, should we support pushing the top-level files as a default?I am proposing this for
v2
buf.yaml
workspaces only.