I am needing to be able to easily manage git repository but also fork them make changes and push them. With standard git CLI there is a pretty standard song and dance to go through for the maintainer and the contributor. So I figured why not wrap up this flow as a golang tool and get some commonality amount teams. Is this a reasonable use case to built on top of this lib ? <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42530085-feature-question?utm_campaign=plugin&utm_content=tracker%2F47809898&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47809898&utm_medium=issues&utm_source=github). </bountysource-plugin>
I am needing to be able to easily manage git repository but also fork them make changes and push them.
With standard git CLI there is a pretty standard song and dance to go through for the maintainer and the contributor.
So I figured why not wrap up this flow as a golang tool and get some commonality amount teams.
Is this a reasonable use case to built on top of this lib ?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.