add git filter-repo as an alternative to git filter-branch (#7135)

pull/7137/head
Stavros Siamantas 2 months ago committed by GitHub
parent ce48c7b594
commit 30edae3e6e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 6
      src/data/roadmaps/git-github/content/git-filter-branch@BKVA6Q7DXemAYjyQOA0nh.md

@ -6,6 +6,10 @@ You can use `git filter-branch` to rewrite Git revision history by applying cust
- Preserving original data: The command preserves all original commit times, merge information, and other details unless specified otherwise. - Preserving original data: The command preserves all original commit times, merge information, and other details unless specified otherwise.
- Rewriting specific branches: Only the positive refs mentioned in the command line are rewritten; if no filters are specified, commits are recommitted without changes. - Rewriting specific branches: Only the positive refs mentioned in the command line are rewritten; if no filters are specified, commits are recommitted without changes.
Notably, there exists a simpler, safer, and more powerful alternative: `git filter-repo`. This tool is actively promoted by Git and offers a streamlined approach to filtering revisions, making it a preferred choice for rewriting your Git history, especially when managing large repositories.
Visit the following resources to learn more: Visit the following resources to learn more:
- [@official@git filter-branch](https://git-scm.com/docs/git-filter-branch) - [@official@git filter-branch](https://git-scm.com/docs/git-filter-branch)
- [@official@git filter-repo](https://github.com/newren/git-filter-repo)
- [@article@Removing sensitive data from a repository](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)
Loading…
Cancel
Save