Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

clear-y's avatar

Rebasing onto laravel/laravel to keep up to date has (predictably) polluted my commit history.

Hey,

As the title states I used git rebase upstream/develop in order to update my application with the latest changes to the develop branch.

This is great in the sense that I have an easy way to keep up to date with the changes, but it's left me a little annoyed (and I should have seen it coming!).

Basically, it's meant that my repo now contains every commit that's found on the laravel/laravel develop branch. Something like 4000 commits! I'd rather not have my repo contain the entire history of laravel/laravel, so I was wondering if you guys knew a way to remove the first 4000 or so commits without screwing up my changes, (all mine are the most recent in the history obviously, because I rebased).

In order to keep it up to date in the future I'll probably use the method discussed here.

Anyway, thanks you in advance for your help!

0 likes
1 reply
bashy's avatar

When I pull phpmyadmin, you HAVE to use this command else you end up grabbing 300MB of commits over the last 100 years :P

Use something like this

git clone --depth=1 --branch=develop git://github.com/laravel/laravel.git foldername

Please or to participate in this conversation.