Closed Grokzen closed 2 years ago
This looks good.
I agree with keeping the legacy .sgit.yml
for now, but I think we should opt to remove the legacy sgit
executable to force users into moving to the new name.
And I think we should introduce git sub
as the preferred, default and documented way of invoking subgit.
Introducing git sub
would also solve #8. The README would have to be updated as well.
Introducing
git sub
would also solve #8. The README would have to be updated as well.
This will be done in a later and future commit and not in this PR for now. But that is on the roadmap for 1.0.0 for sure
@holmboe Ready for review of this. I will not squash the changes once merging. Any mention of sgit that remains should be there until we acctually rename this gitrepo as well. At the point in time i will update the remaning parts to be subgit and not sgit
This PR will not be squash merged as each commit should remain as is. They are divided up into separate steps.
There will remain a few instances until the next PR when we acctually renames the github repo. URL links etc will remain until then.
After this PR we should make an initial release and claim the pypi name for this project.
This PR will super seed #29 where i took the changes from it and merged it into here where applicable.