Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: why to use git filter-branch and what about commit signing? #32

Open
Gems opened this issue Apr 15, 2022 · 0 comments
Open

Question: why to use git filter-branch and what about commit signing? #32

Gems opened this issue Apr 15, 2022 · 0 comments

Comments

@Gems
Copy link

Gems commented Apr 15, 2022

The "git-filter-branch" documentation warns that (quote):

git filter-branch has a plethora of pitfalls that can produce non-obvious manglings of the intended history rewrite (and can leave you with little time to investigate such problems since it has such abysmal performance). These safety and performance issues cannot be backward compatibly fixed and as such, its use is not recommended.
git-filter-branch has a glut of gotchas generating mangled history rewrites.

Besides the performance concerns, there is another concern about commit signing. According to the git filter-branch docs (quote):

If the tag has a signature attached, the signature will be stripped. It is by definition impossible to preserve signatures.

Hence, I wonder why to use git filter-branch and if other options had been considered?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant