Expose internals for external usage #459
Description
I was exploring the possibility of using dependabot/cli as a library within my own project, but ran into a roadblock: all the relevant packages are marked as internal, which prevents external usage.
Example error:
[dependabot/cli](main.go:4:2: use of internal package github.com/dependabot/cli/cmd/dependabot/internal/cmd not allowed)
Would it be possible to consider moving some of the core logic out of the internal package?
I understand there may be reservations about exposing these components more broadly, but I'm not sure if that would necessarily be a negative. It could potentially enable more flexibility and community contributions