Highlighted

[locked]Force Git clone after history change

Community Beginner ,
Oct 13, 2017

Copy link to clipboard

Copied

In a view to remove big files from a (spam link removed by moderator) repository we had to change public history using BFG.

This implies that all developpers should clone it from scratch again to avoid pushing changes from the previous history.

Is there way to block the push from developper repo with non-fresh repo ?

Views

495

Likes

Translate

Translate

Report

Report
This conversation has been locked.

[locked]Force Git clone after history change

Community Beginner ,
Oct 13, 2017

Copy link to clipboard

Copied

In a view to remove big files from a (spam link removed by moderator) repository we had to change public history using BFG.

This implies that all developpers should clone it from scratch again to avoid pushing changes from the previous history.

Is there way to block the push from developper repo with non-fresh repo ?

Views

496

Likes

Translate

Translate

Report

Report
Oct 13, 2017 0
Guide ,
Oct 14, 2017

Copy link to clipboard

Copied

5270166802_1aba80c691.jpg

Likes

Translate

Translate

Report

Report
Oct 14, 2017 0
pziecina LATEST
LEGEND ,
Oct 14, 2017

Copy link to clipboard

Copied

I have removed the link, but will leave the discussion, as we have replied

Likes

Translate

Translate

Report

Report
Oct 14, 2017 0