You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
However, please note that overwriting history in a public repo with lots of forks and a couple of PRs will cause problems to all the other repos. People will have conflicts merging changes from the upstream.
As of me, I'd be fine with just removing the file from the tree with a commit. It was there for more than 2 years. So it won't cause more harm than it already could have caused :)
The reason will be displayed to describe this comment to others. Learn more.
@e1himself yeah agree but if there was potential harm I'd rather bother people with a rewritten history than keeping a suspicions file that could be built by accident. If a fork has more than 2 years it's probably better to re-fork it anyway.
1e82d5a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@e1himself history was rewritten from that point forwards without the issue
1e82d5a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
However, please note that overwriting history in a public repo with lots of forks and a couple of PRs will cause problems to all the other repos. People will have conflicts merging changes from the upstream.
As of me, I'd be fine with just removing the file from the tree with a commit. It was there for more than 2 years. So it won't cause more harm than it already could have caused :)
But that's too late, probably.
🤷♂️
1e82d5a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@e1himself yeah agree but if there was potential harm I'd rather bother people with a rewritten history than keeping a suspicions file that could be built by accident. If a fork has more than 2 years it's probably better to re-fork it anyway.
Ty for noticing that, btw.