I'm pretty new to the git process, and I'm trying to clean up a repo that our company has been using for years.
The issue that I'm trying to resolve is that we have put all of the code into one giant repo.
I'm trying to clean that up and separate them out so that we don't checkout all code base all at once.
The process I'm using to clean up is that I'm cloning the original repo on bitbucket, cloning it on my local environment, deleting all the unrelated folders, commit, and then push it back.
It appears that this process does clean up the uwanted folders.
However, when I do a git clone on the cleaned up repo to another workstation, it looks like the receiving objects line still shows the large amount of files that we had prior to the cleanup. The unwanted folders are definitely gone, but it still seems to download the old repo with all of the unwanted folders first.
Am I missing a step?
Thanks in advance.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot