diff --git a/src/data/roadmaps/git-github/content/git-filter-branch@BKVA6Q7DXemAYjyQOA0nh.md b/src/data/roadmaps/git-github/content/git-filter-branch@BKVA6Q7DXemAYjyQOA0nh.md
index eca6f0310..a74bc7026 100644
--- a/src/data/roadmaps/git-github/content/git-filter-branch@BKVA6Q7DXemAYjyQOA0nh.md
+++ b/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.
 - 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: 
 
-- [@official@git filter-branch](https://git-scm.com/docs/git-filter-branch)
\ No newline at end of file
+- [@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)
\ No newline at end of file