I'm developing a project, which I'm pushing to private repository on my VPS. However, I'd like to publish it on GitHub.
I make a lot of commits(mostly as backups) which doesn't contain complete implementation of feature. I do not want to include history of these commits in public repo.
So, private history would look like:
- Initial commit
- Part Feature A
- Part Feature A
- Part Feature A
- Finished Feature A
- Part Feature B
- Finished Feature B
- ... etc ...
And desired history of public repo would look like:
- Initial commit
- Feature A
- Feature B
- ... etc ...
And there must be no track about partial commits made for development backup. So all internals of a GIT repository would look like there were only just Feature commits, no partial commits.
I know, that I can clone repositories to different folders, and copy-paste between these folders. However, GIT is designed for distributed development. So, I'm wondering whether there's some cleaner and more GIT-like way to solve this.
How to manage separate repositories with different histories?
The first commit on public repo can be completly squeezed, but since then I would like to have a nice commit history in public repo.