Pushing commit to a fork requires pushing commits from the original repository

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

When I push commits into my own fork, I also need to push all the commits that are in the "original" repository, which requires substantial additional bandwidth to transmit data already present in GitLab.

Reproduction steps

1. Create a repository
2. Fork the repository
3. Add 50MiB worth of commits to the original repository
4. Clone the original repository
5. Add a single commit
6. Push the resulting state onto the fork

Pushing to the fork now pushes the original 50MiB worth of commits along with the newly created commit. GitLab already has all the object for these 50MiB worth of commits, so this push is a waste of bandwidth and time (and makes it impossible to push to the fork on low-reliability or slow connections).