Closed joshrosso closed 1 year ago
My current thinking is that we'll end up with a CLI structure looking something like:
proctor source contributions list {repo}
proctor source contributions diff {repo} --tag-1=${TAG1} --tag-2=${TAG2}
proctor source artifacts {repo}
Placing artifacts
under source
may be a bit of a bad UX. I'm open to suggestions here if we feel differently.
Proposal
Introduce
proctor source ...
to the proctor CLI. Accompanying this will be asource
library that can be imported as go module.Initial ideas of command we can expose using the library include:
Implementation details
This will largely be refactoring our library from the existing git-adapter (closed-source platform agent) and bringing it into this CLI.
Then, as a final step, we'd require it accordingly in the adapter.