| Name | git-filter-repo JSON |
| Version |
2.47.0
JSON |
| download |
| home_page | None |
| Summary | Quickly rewrite git repository history |
| upload_time | 2024-12-04 03:10:48 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.6 |
| license | MIT |
| keywords |
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
git filter-repo is a versatile tool for rewriting history, which includes
[capabilities I have not found anywhere
else](#design-rationale-behind-filter-repo). It roughly falls into the
same space of tool as [git
filter-branch](https://git-scm.com/docs/git-filter-branch) but without the
capitulation-inducing poor
[performance](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/),
with far more capabilities, and with a design that scales usability-wise
beyond trivial rewriting cases. [git filter-repo is now recommended by the
git project](https://git-scm.com/docs/git-filter-branch#_warning) instead
of git filter-branch.
While most users will probably just use filter-repo as a simple command
line tool (and likely only use a few of its flags), at its core filter-repo
contains a library for creating history rewriting tools. As such, users
with specialized needs can leverage it to quickly create [entirely new
history rewriting tools](contrib/filter-repo-demos).
# Table of Contents
* [Prerequisites](#prerequisites)
* [How do I install it?](#how-do-i-install-it)
* [How do I use it?](#how-do-i-use-it)
* [Why filter-repo instead of other alternatives?](#why-filter-repo-instead-of-other-alternatives)
* [filter-branch](#filter-branch)
* [BFG Repo Cleaner](#bfg-repo-cleaner)
* [Simple example, with comparisons](#simple-example-with-comparisons)
* [Solving this with filter-repo](#solving-this-with-filter-repo)
* [Solving this with BFG Repo Cleaner](#solving-this-with-bfg-repo-cleaner)
* [Solving this with filter-branch](#solving-this-with-filter-branch)
* [Solving this with fast-export/fast-import](#solving-this-with-fast-exportfast-import)
* [Design rationale behind filter-repo](#design-rationale-behind-filter-repo)
* [How do I contribute?](#how-do-i-contribute)
* [Is there a Code of Conduct?](#is-there-a-code-of-conduct)
* [Upstream Improvements](#upstream-improvements)
# Prerequisites
filter-repo requires:
* git >= 2.22.0 at a minimum; [some features](#upstream-improvements)
require git >= 2.24.0 or later
* python3 >= 3.6
# How do I install it?
While the `git-filter-repo` repository has many files, the main logic
is all contained in a single-file python script named
`git-filter-repo`, which was done to make installation for basic use
on many systems trivial: just place that one file into your $PATH.
See [INSTALL.md](INSTALL.md) for things beyond basic usage or special
cases. The more involved instructions are only needed if one of the
following apply:
* you do not find the above comment about trivial installation intuitively
obvious
* you are working with a python3 executable named something other than
"python3"
* you want to install documentation (beyond the builtin docs shown with -h)
* you want to run some of the [contrib](contrib/filter-repo-demos/) examples
* you want to create your own python filtering scripts using filter-repo as
a module/library
# How do I use it?
For comprehensive documentation:
* see the [user manual](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
* alternative formating of the user manual is available on various
external sites
([example](https://www.mankier.com/1/git-filter-repo)), for those
that don't like the htmlpreview.github.io layout, though it may
only be up-to-date as of the latest release
If you prefer learning from examples:
* there is a [cheat sheet for converting filter-branch
commands](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage),
which covers every example from the filter-branch manual
* there is a [cheat sheet for converting BFG Repo Cleaner
commands](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg),
which covers every example from the BFG website
* the [simple example](#simple-example-with-comparisons) below may
be of interest
* the user manual has an extensive [examples
section](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#EXAMPLES)
* I have collected a set of [example filterings based on user-filed issues](Documentation/examples-from-user-filed-issues.md)
In either case, you may also find the [Frequently Answered Questions](Documentation/FAQ.md) useful.
# Why filter-repo instead of other alternatives?
This was covered in more detail in a [Git Rev News article on
filter-repo](https://git.github.io/rev_news/2019/08/21/edition-54/#an-introduction-to-git-filter-repo--written-by-elijah-newren),
but some highlights for the main competitors:
## filter-branch
* filter-branch is [extremely to unusably
slow](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/)
([multiple orders of magnitude slower than it should
be](https://git-scm.com/docs/git-filter-branch#PERFORMANCE))
for non-trivial repositories.
* [filter-branch is riddled with
gotchas](https://git-scm.com/docs/git-filter-branch#SAFETY) that can
silently corrupt your rewrite or at least thwart your "cleanup"
efforts by giving you something more problematic and messy than what
you started with.
* filter-branch is [very onerous](#simple-example-with-comparisons)
[to
use](https://github.com/newren/git-filter-repo/blob/a6a6a1b0f62d365bbe2e76f823e1621857ec4dbd/contrib/filter-repo-demos/filter-lamely#L9-L61)
for any rewrite which is even slightly non-trivial.
* the git project has stated that the above issues with filter-branch
cannot be backward compatibly fixed; they recommend that you [stop
using
filter-branch](https://git-scm.com/docs/git-filter-branch#_warning)
* die-hard fans of filter-branch may be interested in
[filter-lamely](contrib/filter-repo-demos/filter-lamely)
(a.k.a. [filter-branch-ish](contrib/filter-repo-demos/filter-branch-ish)),
a reimplementation of filter-branch based on filter-repo which is
more performant (though not nearly as fast or safe as
filter-repo).
* a [cheat
sheet](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage)
is available showing how to convert example commands from the manual of
filter-branch into filter-repo commands.
## BFG Repo Cleaner
* great tool for its time, but while it makes some things simple, it
is limited to a few kinds of rewrites.
* its architecture is not amenable to handling more types of
rewrites.
* its architecture presents some shortcomings and bugs even for its
intended usecase.
* fans of bfg may be interested in
[bfg-ish](contrib/filter-repo-demos/bfg-ish), a reimplementation of bfg
based on filter-repo which includes several new features and bugfixes
relative to bfg.
* a [cheat
sheet](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg)
is available showing how to convert example commands from the manual of
BFG Repo Cleaner into filter-repo commands.
# Simple example, with comparisons
Let's say that we want to extract a piece of a repository, with the intent
on merging just that piece into some other bigger repo. For extraction, we
want to:
* extract the history of a single directory, src/. This means that only
paths under src/ remain in the repo, and any commits that only touched
paths outside this directory will be removed.
* rename all files to have a new leading directory, my-module/ (e.g. so that
src/foo.c becomes my-module/src/foo.c)
* rename any tags in the extracted repository to have a 'my-module-'
prefix (to avoid any conflicts when we later merge this repo into
something else)
## Solving this with filter-repo
Doing this with filter-repo is as simple as the following command:
```shell
git filter-repo --path src/ --to-subdirectory-filter my-module --tag-rename '':'my-module-'
```
(the single quotes are unnecessary, but make it clearer to a human that we
are replacing the empty string as a prefix with `my-module-`)
## Solving this with BFG Repo Cleaner
BFG Repo Cleaner is not capable of this kind of rewrite; in fact, all
three types of wanted changes are outside of its capabilities.
## Solving this with filter-branch
filter-branch comes with a pile of caveats (more on that below) even
once you figure out the necessary invocation(s):
```shell
git filter-branch \
--tree-filter 'mkdir -p my-module && \
git ls-files \
| grep -v ^src/ \
| xargs git rm -f -q && \
ls -d * \
| grep -v my-module \
| xargs -I files mv files my-module/' \
--tag-name-filter 'echo "my-module-$(cat)"' \
--prune-empty -- --all
git clone file://$(pwd) newcopy
cd newcopy
git for-each-ref --format="delete %(refname)" refs/tags/ \
| grep -v refs/tags/my-module- \
| git update-ref --stdin
git gc --prune=now
```
Some might notice that the above filter-branch invocation will be really
slow due to using --tree-filter; you could alternatively use the
--index-filter option of filter-branch, changing the above commands to:
```shell
git filter-branch \
--index-filter 'git ls-files \
| grep -v ^src/ \
| xargs git rm -q --cached;
git ls-files -s \
| sed "s%$(printf \\t)%&my-module/%" \
| git update-index --index-info;
git ls-files \
| grep -v ^my-module/ \
| xargs git rm -q --cached' \
--tag-name-filter 'echo "my-module-$(cat)"' \
--prune-empty -- --all
git clone file://$(pwd) newcopy
cd newcopy
git for-each-ref --format="delete %(refname)" refs/tags/ \
| grep -v refs/tags/my-module- \
| git update-ref --stdin
git gc --prune=now
```
However, for either filter-branch command there are a pile of caveats.
First, some may be wondering why I list five commands here for
filter-branch. Despite the use of --all and --tag-name-filter, and
filter-branch's manpage claiming that a clone is enough to get rid of
old objects, the extra steps to delete the other tags and do another
gc are still required to clean out the old objects and avoid mixing
new and old history before pushing somewhere. Other caveats:
* Commit messages are not rewritten; so if some of your commit
messages refer to prior commits by (abbreviated) sha1, after the
rewrite those messages will now refer to commits that are no longer
part of the history. It would be better to rewrite those
(abbreviated) sha1 references to refer to the new commit ids.
* The --prune-empty flag sometimes misses commits that should be
pruned, and it will also prune commits that *started* empty rather
than just ended empty due to filtering. For repositories that
intentionally use empty commits for versioning and publishing
related purposes, this can be detrimental.
* The commands above are OS-specific. GNU vs. BSD issues for sed,
xargs, and other commands often trip up users; I think I failed to
get most folks to use --index-filter since the only example in the
filter-branch manpage that both uses it and shows how to move
everything into a subdirectory is linux-specific, and it is not
obvious to the reader that it has a portability issue since it
silently misbehaves rather than failing loudly.
* The --index-filter version of the filter-branch command may be two to
three times faster than the --tree-filter version, but both
filter-branch commands are going to be multiple orders of magnitude
slower than filter-repo.
* Both commands assume all filenames are composed entirely of ascii
characters (even special ascii characters such as tabs or double
quotes will wreak havoc and likely result in missing files or
misnamed files)
## Solving this with fast-export/fast-import
One can kind of hack this together with something like:
```shell
git fast-export --no-data --reencode=yes --mark-tags --fake-missing-tagger \
--signed-tags=strip --tag-of-filtered-object=rewrite --all \
| grep -vP '^M [0-9]+ [0-9a-f]+ (?!src/)' \
| grep -vP '^D (?!src/)' \
| perl -pe 's%^(M [0-9]+ [0-9a-f]+ )(.*)$%\1my-module/\2%' \
| perl -pe 's%^(D )(.*)$%\1my-module/\2%' \
| perl -pe s%refs/tags/%refs/tags/my-module-% \
| git -c core.ignorecase=false fast-import --date-format=raw-permissive \
--force --quiet
git for-each-ref --format="delete %(refname)" refs/tags/ \
| grep -v refs/tags/my-module- \
| git update-ref --stdin
git reset --hard
git reflog expire --expire=now --all
git gc --prune=now
```
But this comes with some nasty caveats and limitations:
* The various greps and regex replacements operate on the entire
fast-export stream and thus might accidentally corrupt unintended
portions of it, such as commit messages. If you needed to edit
file contents and thus dropped the --no-data flag, it could also
end up corrupting file contents.
* This command assumes all filenames in the repository are composed
entirely of ascii characters, and also exclude special characters
such as tabs or double quotes. If such a special filename exists
within the old src/ directory, it will be pruned even though it
was intended to be kept. (In slightly different repository
rewrites, this type of editing also risks corrupting filenames
with special characters by adding extra double quotes near the end
of the filename and in some leading directory name.)
* This command will leave behind huge numbers of useless empty
commits, and has no realistic way of pruning them. (And if you
tried to combine this technique with another tool to prune the
empty commits, then you now have no way to distinguish between
commits which were made empty by the filtering that you want to
remove, and commits which were empty before the filtering process
and which you thus may want to keep.)
* Commit messages which reference other commits by hash will now
reference old commits that no longer exist. Attempting to edit
the commit messages to update them is extraordinarily difficult to
add to this kind of direct rewrite.
# Design rationale behind filter-repo
None of the existing repository filtering tools did what I wanted;
they all came up short for my needs. No tool provided any of the
first eight traits below I wanted, and no tool provided more than
two of the last four traits either:
1. [Starting report] Provide user an analysis of their repo to help
them get started on what to prune or rename, instead of expecting
them to guess or find other tools to figure it out. (Triggered, e.g.
by running the first time with a special flag, such as --analyze.)
1. [Keep vs. remove] Instead of just providing a way for users to
easily remove selected paths, also provide flags for users to
only *keep* certain paths. Sure, users could workaround this by
specifying to remove all paths other than the ones they want to
keep, but the need to specify all paths that *ever* existed in
**any** version of the repository could sometimes be quite
painful. For filter-branch, using pipelines like `git ls-files |
grep -v ... | xargs -r git rm` might be a reasonable workaround
but can get unwieldy and isn't as straightforward for users; plus
those commands are often operating-system specific (can you spot
the GNUism in the snippet I provided?).
1. [Renaming] It should be easy to rename paths. For example, in
addition to allowing one to treat some subdirectory as the root
of the repository, also provide options for users to make the
root of the repository just become a subdirectory. And more
generally allow files and directories to be easily renamed.
Provide sanity checks if renaming causes multiple files to exist
at the same path. (And add special handling so that if a commit
merely copied oldname->newname without modification, then
filtering oldname->newname doesn't trigger the sanity check and
die on that commit.)
1. [More intelligent safety] Writing copies of the original refs to
a special namespace within the repo does not provide a
user-friendly recovery mechanism. Many would struggle to recover
using that. Almost everyone I've ever seen do a repository
filtering operation has done so with a fresh clone, because
wiping out the clone in case of error is a vastly easier recovery
mechanism. Strongly encourage that workflow by [detecting and
bailing if we're not in a fresh
clone](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#FRESHCLONE),
unless the user overrides with --force.
1. [Auto shrink] Automatically remove old cruft and repack the
repository for the user after filtering (unless overridden); this
simplifies things for the user, helps avoid mixing old and new
history together, and avoids problems where the multi-step
process for shrinking the repo documented in the manpage doesn't
actually work in some cases. (I'm looking at you,
filter-branch.)
1. [Clean separation] Avoid confusing users (and prevent accidental
re-pushing of old stuff) due to mixing old repo and rewritten
repo together. (This is particularly a problem with filter-branch
when using the --tag-name-filter option, and sometimes also an
issue when only filtering a subset of branches.)
1. [Versatility] Provide the user the ability to extend the tool or
even write new tools that leverage existing capabilities, and
provide this extensibility in a way that (a) avoids the need to
fork separate processes (which would destroy performance), (b)
avoids making the user specify OS-dependent shell commands (which
would prevent users from sharing commands with each other), (c)
takes advantage of rich data structures (because hashes, dicts,
lists, and arrays are prohibitively difficult in shell) and (d)
provides reasonable string manipulation capabilities (which are
sorely lacking in shell).
1. [Old commit references] Provide a way for users to use old commit
IDs with the new repository (in particular via mapping from old to
new hashes with refs/replace/ references).
1. [Commit message consistency] If commit messages refer to other
commits by ID (e.g. "this reverts commit 01234567890abcdef", "In
commit 0013deadbeef9a..."), those commit messages should be
rewritten to refer to the new commit IDs.
1. [Become-empty pruning] Commits which become empty due to filtering
should be pruned. If the parent of a commit is pruned, the first
non-pruned ancestor needs to become the new parent. If no
non-pruned ancestor exists and the commit was not a merge, then it
becomes a new root commit. If no non-pruned ancestor exists and
the commit was a merge, then the merge will have one less parent
(and thus make it likely to become a non-merge commit which would
itself be pruned if it had no file changes of its own). One
special thing to note here is that we prune commits which become
empty, NOT commits which start empty. Some projects intentionally
create empty commits for versioning or publishing reasons, and
these should not be removed. (As a special case, commits which
started empty but whose parent was pruned away will also be
considered to have "become empty".)
1. [Become-degenerate pruning] Pruning of commits which become empty
can potentially cause topology changes, and there are lots of
special cases. Normally, merge commits are not removed since they
are needed to preserve the graph topology, but the pruning of
parents and other ancestors can ultimately result in the loss of
one or more parents. A simple case was already noted above: if a
merge commit loses enough parents to become a non-merge commit and
it has no file changes, then it too can be pruned. Merge commits
can also have a topology that becomes degenerate: it could end up
with the merge_base serving as both parents (if all intervening
commits from the original repo were pruned), or it could end up
with one parent which is an ancestor of its other parent. In such
cases, if the merge has no file changes of its own, then the merge
commit can also be pruned. However, much as we do with empty
pruning we do not prune merge commits that started degenerate
(which indicates it may have been intentional, such as with --no-ff
merges) but only merge commits that become degenerate and have no
file changes of their own.
1. [Speed] Filtering should be reasonably fast
# How do I contribute?
See the [contributing guidelines](Documentation/Contributing.md).
# Is there a Code of Conduct?
Participants in the filter-repo community are expected to adhere to
the same standards as for the git project, so the [git Code of
Conduct](https://git.kernel.org/pub/scm/git/git.git/tree/CODE_OF_CONDUCT.md)
applies.
# Upstream Improvements
Work on filter-repo and [its
predecessor](https://public-inbox.org/git/51419b2c0904072035u1182b507o836a67ac308d32b9@mail.gmail.com/)
has also driven numerous improvements to fast-export and fast-import
(and occasionally other commands) in core git, based on things
filter-repo needs to do its work:
* git-2.48.0 (to be released Jan 2025)
* [fast-import: disallow more path components](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=da91a90c2f)
* [fast-import: disallow "." and ".." path components](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=4a2790a257)
* [fast-import: avoid making replace refs point to themselves](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=5e904f1a4a)
* git-2.28.0
* [fast-import: add new --date-format=raw-permissive format](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=d42a2fb72f)
* git-2.24.0
* [fast-export: handle nested tags](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=941790d7de)
* [t9350: add tests for tags of things other than a commit](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=8d7d33c1ce)
* [fast-export: allow user to request tags be marked with --mark-tags](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=a1638cfe12)
* [fast-export: add support for --import-marks-if-exists](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=208d69246e)
* [fast-import: add support for new 'alias' command](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=b8f50e5b60)
* [fast-import: allow tags to be identified by mark labels](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=f73b2aba05)
* [fast-import: fix handling of deleted tags](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=3164e6bd24)
* [fast-export: fix exporting a tag and nothing else](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=af2abd870b)
* [git-fast-import.txt: clarify that multiple merge commits are allowed](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=d1387d3895)
* git-2.23.0
* [t9350: fix encoding test to actually test reencoding](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=32615ce762)
* [fast-import: support 'encoding' commit header](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=3edfcc65fd)
* [fast-export: avoid stripping encoding header if we cannot reencode](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=ccbfc96dc4)
* [fast-export: differentiate between explicitly UTF-8 and implicitly
UTF-8](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=57a8be2cb0)
* [fast-export: do automatic reencoding of commit messages only if
requested](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=e80001f8fd)
* git-2.22.0
* [log,diff-tree: add --combined-all-paths option](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=d76ce4f734)
* [t9300: demonstrate bug with get-mark and empty orphan commits](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=62edbec7de)
* [git-fast-import.txt: fix wording about where ls command can appear](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=a63c54a019)
* [fast-import: check most prominent commands first](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=5056bb7646)
* [fast-import: only allow cat-blob requests where it makes sense](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=7ffde293f2)
* [fast-import: fix erroneous handling of get-mark with empty orphan
commits](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=cf7b857a77)
* [Honor core.precomposeUnicode in more places](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=8e712ef6fc)
* git-2.21.0
* [fast-export: convert sha1 to oid](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=843b9e6d48)
* [git-fast-import.txt: fix documentation for --quiet option](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=f55c979b14)
* [git-fast-export.txt: clarify misleading documentation about rev-list
args](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=4532be7cba)
* [fast-export: use value from correct enum](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=b93b81e799)
* [fast-export: avoid dying when filtering by paths and old tags exist](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=1f30c904b3)
* [fast-export: move commit rewriting logic into a function for reuse](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=f129c4275c)
* [fast-export: when using paths, avoid corrupt stream with non-existent
mark](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=cd13762d8f)
* [fast-export: ensure we export requested refs](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=fdf31b6369)
* [fast-export: add --reference-excluded-parents option](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=530ca19c02)
* [fast-import: remove unmaintained duplicate documentation](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=25dd3e4889)
* [fast-export: add a --show-original-ids option to show
original names](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=a965bb3116)
* [git-show-ref.txt: fix order of flags](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=bd8d6f0def)
* git-2.20.0
* [update-ref: fix type of update_flags variable to
match its usage](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=e4c34855a2)
* [update-ref: allow --no-deref with --stdin](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=d345e9fbe7)
* git-1.7.3
* [fast-export: Fix dropping of files with --import-marks and path
limiting](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=4087a02e45)
* [fast-export: Add a --full-tree option](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=7f40ab0916)
* [fast-export: Fix output order of D/F changes](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=060df62422)
* [fast-import: Improve robustness when D->F changes provided in wrong
order](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=253fb5f889)
* git-1.6.4:
* [fast-export: Set revs.topo_order before calling setup_revisions](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=668f3aa776)
* [fast-export: Omit tags that tag trees](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=02c48cd69b)
* [fast-export: Make sure we show actual ref names instead of "(null)"](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=2374502c6c)
* [fast-export: Do parent rewriting to avoid dropping relevant commits](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=32164131db)
* [fast-export: Add a --tag-of-filtered-object option for newly
dangling tags](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=2d8ad46919)
* [Add new fast-export testcases](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=25e0ca5dd6)
* [fast-export: Document the fact that git-rev-list arguments are
accepted](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=8af15d282e)
* git-1.6.3:
* [git-filter-branch: avoid collisions with variables in eval'ed
commands](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=d5b0c97d13)
* [Correct missing SP characters in grammar comment at top of
fast-import.c](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=98e1a4186a)
* [fast-export: Avoid dropping files from commits](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=ebeec7dbc5)
* git-1.6.1.4:
* [fast-export: ensure we traverse commits in topological order](
https://git.kernel.org/pub/scm/git/git.git/commit/?id=784f8affe4)
Raw data
{
"_id": null,
"home_page": null,
"name": "git-filter-repo",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": null,
"keywords": null,
"author": null,
"author_email": "Elijah Newren <newren@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/b9/bb/7a283f568af6b0528ade65e8ace84bd6ba46003e429101bcd62c232d01a5/git_filter_repo-2.47.0.tar.gz",
"platform": null,
"description": "git filter-repo is a versatile tool for rewriting history, which includes\n[capabilities I have not found anywhere\nelse](#design-rationale-behind-filter-repo). It roughly falls into the\nsame space of tool as [git\nfilter-branch](https://git-scm.com/docs/git-filter-branch) but without the\ncapitulation-inducing poor\n[performance](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/),\nwith far more capabilities, and with a design that scales usability-wise\nbeyond trivial rewriting cases. [git filter-repo is now recommended by the\ngit project](https://git-scm.com/docs/git-filter-branch#_warning) instead\nof git filter-branch.\n\nWhile most users will probably just use filter-repo as a simple command\nline tool (and likely only use a few of its flags), at its core filter-repo\ncontains a library for creating history rewriting tools. As such, users\nwith specialized needs can leverage it to quickly create [entirely new\nhistory rewriting tools](contrib/filter-repo-demos).\n\n# Table of Contents\n\n * [Prerequisites](#prerequisites)\n * [How do I install it?](#how-do-i-install-it)\n * [How do I use it?](#how-do-i-use-it)\n * [Why filter-repo instead of other alternatives?](#why-filter-repo-instead-of-other-alternatives)\n * [filter-branch](#filter-branch)\n * [BFG Repo Cleaner](#bfg-repo-cleaner)\n * [Simple example, with comparisons](#simple-example-with-comparisons)\n * [Solving this with filter-repo](#solving-this-with-filter-repo)\n * [Solving this with BFG Repo Cleaner](#solving-this-with-bfg-repo-cleaner)\n * [Solving this with filter-branch](#solving-this-with-filter-branch)\n * [Solving this with fast-export/fast-import](#solving-this-with-fast-exportfast-import)\n * [Design rationale behind filter-repo](#design-rationale-behind-filter-repo)\n * [How do I contribute?](#how-do-i-contribute)\n * [Is there a Code of Conduct?](#is-there-a-code-of-conduct)\n * [Upstream Improvements](#upstream-improvements)\n\n# Prerequisites\n\nfilter-repo requires:\n\n * git >= 2.22.0 at a minimum; [some features](#upstream-improvements)\n require git >= 2.24.0 or later\n * python3 >= 3.6\n\n# How do I install it?\n\nWhile the `git-filter-repo` repository has many files, the main logic\nis all contained in a single-file python script named\n`git-filter-repo`, which was done to make installation for basic use\non many systems trivial: just place that one file into your $PATH.\n\nSee [INSTALL.md](INSTALL.md) for things beyond basic usage or special\ncases. The more involved instructions are only needed if one of the\nfollowing apply:\n\n * you do not find the above comment about trivial installation intuitively\n obvious\n * you are working with a python3 executable named something other than\n \"python3\"\n * you want to install documentation (beyond the builtin docs shown with -h)\n * you want to run some of the [contrib](contrib/filter-repo-demos/) examples\n * you want to create your own python filtering scripts using filter-repo as\n a module/library\n\n# How do I use it?\n\nFor comprehensive documentation:\n * see the [user manual](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)\n * alternative formating of the user manual is available on various\n external sites\n ([example](https://www.mankier.com/1/git-filter-repo)), for those\n that don't like the htmlpreview.github.io layout, though it may\n only be up-to-date as of the latest release\n\nIf you prefer learning from examples:\n * there is a [cheat sheet for converting filter-branch\n commands](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage),\n which covers every example from the filter-branch manual\n * there is a [cheat sheet for converting BFG Repo Cleaner\n commands](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg),\n which covers every example from the BFG website\n * the [simple example](#simple-example-with-comparisons) below may\n be of interest\n * the user manual has an extensive [examples\nsection](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#EXAMPLES)\n * I have collected a set of [example filterings based on user-filed issues](Documentation/examples-from-user-filed-issues.md)\n\nIn either case, you may also find the [Frequently Answered Questions](Documentation/FAQ.md) useful.\n\n# Why filter-repo instead of other alternatives?\n\nThis was covered in more detail in a [Git Rev News article on\nfilter-repo](https://git.github.io/rev_news/2019/08/21/edition-54/#an-introduction-to-git-filter-repo--written-by-elijah-newren),\nbut some highlights for the main competitors:\n\n## filter-branch\n\n * filter-branch is [extremely to unusably\n slow](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/)\n ([multiple orders of magnitude slower than it should\n be](https://git-scm.com/docs/git-filter-branch#PERFORMANCE))\n for non-trivial repositories.\n\n * [filter-branch is riddled with\n gotchas](https://git-scm.com/docs/git-filter-branch#SAFETY) that can\n silently corrupt your rewrite or at least thwart your \"cleanup\"\n efforts by giving you something more problematic and messy than what\n you started with.\n\n * filter-branch is [very onerous](#simple-example-with-comparisons)\n [to\n use](https://github.com/newren/git-filter-repo/blob/a6a6a1b0f62d365bbe2e76f823e1621857ec4dbd/contrib/filter-repo-demos/filter-lamely#L9-L61)\n for any rewrite which is even slightly non-trivial.\n\n * the git project has stated that the above issues with filter-branch\n cannot be backward compatibly fixed; they recommend that you [stop\n using\n filter-branch](https://git-scm.com/docs/git-filter-branch#_warning)\n\n * die-hard fans of filter-branch may be interested in\n [filter-lamely](contrib/filter-repo-demos/filter-lamely)\n (a.k.a. [filter-branch-ish](contrib/filter-repo-demos/filter-branch-ish)),\n a reimplementation of filter-branch based on filter-repo which is\n more performant (though not nearly as fast or safe as\n filter-repo).\n\n * a [cheat\n sheet](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage)\n is available showing how to convert example commands from the manual of\n filter-branch into filter-repo commands.\n\n## BFG Repo Cleaner\n\n * great tool for its time, but while it makes some things simple, it\n is limited to a few kinds of rewrites.\n\n * its architecture is not amenable to handling more types of\n rewrites.\n\n * its architecture presents some shortcomings and bugs even for its\n intended usecase.\n\n * fans of bfg may be interested in\n [bfg-ish](contrib/filter-repo-demos/bfg-ish), a reimplementation of bfg\n based on filter-repo which includes several new features and bugfixes\n relative to bfg.\n\n * a [cheat\n sheet](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg)\n is available showing how to convert example commands from the manual of\n BFG Repo Cleaner into filter-repo commands.\n\n# Simple example, with comparisons\n\nLet's say that we want to extract a piece of a repository, with the intent\non merging just that piece into some other bigger repo. For extraction, we\nwant to:\n\n * extract the history of a single directory, src/. This means that only\n paths under src/ remain in the repo, and any commits that only touched\n paths outside this directory will be removed.\n * rename all files to have a new leading directory, my-module/ (e.g. so that\n src/foo.c becomes my-module/src/foo.c)\n * rename any tags in the extracted repository to have a 'my-module-'\n prefix (to avoid any conflicts when we later merge this repo into\n something else)\n\n## Solving this with filter-repo\n\nDoing this with filter-repo is as simple as the following command:\n```shell\n git filter-repo --path src/ --to-subdirectory-filter my-module --tag-rename '':'my-module-'\n```\n(the single quotes are unnecessary, but make it clearer to a human that we\nare replacing the empty string as a prefix with `my-module-`)\n\n## Solving this with BFG Repo Cleaner\n\nBFG Repo Cleaner is not capable of this kind of rewrite; in fact, all\nthree types of wanted changes are outside of its capabilities.\n\n## Solving this with filter-branch\n\nfilter-branch comes with a pile of caveats (more on that below) even\nonce you figure out the necessary invocation(s):\n\n```shell\n git filter-branch \\\n --tree-filter 'mkdir -p my-module && \\\n git ls-files \\\n | grep -v ^src/ \\\n | xargs git rm -f -q && \\\n ls -d * \\\n | grep -v my-module \\\n | xargs -I files mv files my-module/' \\\n --tag-name-filter 'echo \"my-module-$(cat)\"' \\\n\t --prune-empty -- --all\n git clone file://$(pwd) newcopy\n cd newcopy\n git for-each-ref --format=\"delete %(refname)\" refs/tags/ \\\n | grep -v refs/tags/my-module- \\\n | git update-ref --stdin\n git gc --prune=now\n```\n\nSome might notice that the above filter-branch invocation will be really\nslow due to using --tree-filter; you could alternatively use the\n--index-filter option of filter-branch, changing the above commands to:\n\n```shell\n git filter-branch \\\n --index-filter 'git ls-files \\\n | grep -v ^src/ \\\n | xargs git rm -q --cached;\n git ls-files -s \\\n | sed \"s%$(printf \\\\t)%&my-module/%\" \\\n | git update-index --index-info;\n git ls-files \\\n | grep -v ^my-module/ \\\n | xargs git rm -q --cached' \\\n --tag-name-filter 'echo \"my-module-$(cat)\"' \\\n --prune-empty -- --all\n git clone file://$(pwd) newcopy\n cd newcopy\n git for-each-ref --format=\"delete %(refname)\" refs/tags/ \\\n | grep -v refs/tags/my-module- \\\n | git update-ref --stdin\n git gc --prune=now\n```\n\nHowever, for either filter-branch command there are a pile of caveats.\nFirst, some may be wondering why I list five commands here for\nfilter-branch. Despite the use of --all and --tag-name-filter, and\nfilter-branch's manpage claiming that a clone is enough to get rid of\nold objects, the extra steps to delete the other tags and do another\ngc are still required to clean out the old objects and avoid mixing\nnew and old history before pushing somewhere. Other caveats:\n * Commit messages are not rewritten; so if some of your commit\n messages refer to prior commits by (abbreviated) sha1, after the\n rewrite those messages will now refer to commits that are no longer\n part of the history. It would be better to rewrite those\n (abbreviated) sha1 references to refer to the new commit ids.\n * The --prune-empty flag sometimes misses commits that should be\n pruned, and it will also prune commits that *started* empty rather\n than just ended empty due to filtering. For repositories that\n intentionally use empty commits for versioning and publishing\n related purposes, this can be detrimental.\n * The commands above are OS-specific. GNU vs. BSD issues for sed,\n xargs, and other commands often trip up users; I think I failed to\n get most folks to use --index-filter since the only example in the\n filter-branch manpage that both uses it and shows how to move\n everything into a subdirectory is linux-specific, and it is not\n obvious to the reader that it has a portability issue since it\n silently misbehaves rather than failing loudly.\n * The --index-filter version of the filter-branch command may be two to\n three times faster than the --tree-filter version, but both\n filter-branch commands are going to be multiple orders of magnitude\n slower than filter-repo.\n * Both commands assume all filenames are composed entirely of ascii\n characters (even special ascii characters such as tabs or double\n quotes will wreak havoc and likely result in missing files or\n misnamed files)\n\n## Solving this with fast-export/fast-import\n\nOne can kind of hack this together with something like:\n\n```shell\n git fast-export --no-data --reencode=yes --mark-tags --fake-missing-tagger \\\n --signed-tags=strip --tag-of-filtered-object=rewrite --all \\\n | grep -vP '^M [0-9]+ [0-9a-f]+ (?!src/)' \\\n | grep -vP '^D (?!src/)' \\\n | perl -pe 's%^(M [0-9]+ [0-9a-f]+ )(.*)$%\\1my-module/\\2%' \\\n | perl -pe 's%^(D )(.*)$%\\1my-module/\\2%' \\\n | perl -pe s%refs/tags/%refs/tags/my-module-% \\\n | git -c core.ignorecase=false fast-import --date-format=raw-permissive \\\n --force --quiet\n git for-each-ref --format=\"delete %(refname)\" refs/tags/ \\\n | grep -v refs/tags/my-module- \\\n | git update-ref --stdin\n git reset --hard\n git reflog expire --expire=now --all\n git gc --prune=now\n```\n\nBut this comes with some nasty caveats and limitations:\n * The various greps and regex replacements operate on the entire\n fast-export stream and thus might accidentally corrupt unintended\n portions of it, such as commit messages. If you needed to edit\n file contents and thus dropped the --no-data flag, it could also\n end up corrupting file contents.\n * This command assumes all filenames in the repository are composed\n entirely of ascii characters, and also exclude special characters\n such as tabs or double quotes. If such a special filename exists\n within the old src/ directory, it will be pruned even though it\n was intended to be kept. (In slightly different repository\n rewrites, this type of editing also risks corrupting filenames\n with special characters by adding extra double quotes near the end\n of the filename and in some leading directory name.)\n * This command will leave behind huge numbers of useless empty\n commits, and has no realistic way of pruning them. (And if you\n tried to combine this technique with another tool to prune the\n empty commits, then you now have no way to distinguish between\n commits which were made empty by the filtering that you want to\n remove, and commits which were empty before the filtering process\n and which you thus may want to keep.)\n * Commit messages which reference other commits by hash will now\n reference old commits that no longer exist. Attempting to edit\n the commit messages to update them is extraordinarily difficult to\n add to this kind of direct rewrite.\n\n# Design rationale behind filter-repo\n\nNone of the existing repository filtering tools did what I wanted;\nthey all came up short for my needs. No tool provided any of the\nfirst eight traits below I wanted, and no tool provided more than\ntwo of the last four traits either:\n\n 1. [Starting report] Provide user an analysis of their repo to help\n them get started on what to prune or rename, instead of expecting\n them to guess or find other tools to figure it out. (Triggered, e.g.\n by running the first time with a special flag, such as --analyze.)\n\n 1. [Keep vs. remove] Instead of just providing a way for users to\n easily remove selected paths, also provide flags for users to\n only *keep* certain paths. Sure, users could workaround this by\n specifying to remove all paths other than the ones they want to\n keep, but the need to specify all paths that *ever* existed in\n **any** version of the repository could sometimes be quite\n painful. For filter-branch, using pipelines like `git ls-files |\n grep -v ... | xargs -r git rm` might be a reasonable workaround\n but can get unwieldy and isn't as straightforward for users; plus\n those commands are often operating-system specific (can you spot\n the GNUism in the snippet I provided?).\n\n 1. [Renaming] It should be easy to rename paths. For example, in\n addition to allowing one to treat some subdirectory as the root\n of the repository, also provide options for users to make the\n root of the repository just become a subdirectory. And more\n generally allow files and directories to be easily renamed.\n Provide sanity checks if renaming causes multiple files to exist\n at the same path. (And add special handling so that if a commit\n merely copied oldname->newname without modification, then\n filtering oldname->newname doesn't trigger the sanity check and\n die on that commit.)\n\n 1. [More intelligent safety] Writing copies of the original refs to\n a special namespace within the repo does not provide a\n user-friendly recovery mechanism. Many would struggle to recover\n using that. Almost everyone I've ever seen do a repository\n filtering operation has done so with a fresh clone, because\n wiping out the clone in case of error is a vastly easier recovery\n mechanism. Strongly encourage that workflow by [detecting and\n bailing if we're not in a fresh\n clone](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#FRESHCLONE),\n unless the user overrides with --force.\n\n 1. [Auto shrink] Automatically remove old cruft and repack the\n repository for the user after filtering (unless overridden); this\n simplifies things for the user, helps avoid mixing old and new\n history together, and avoids problems where the multi-step\n process for shrinking the repo documented in the manpage doesn't\n actually work in some cases. (I'm looking at you,\n filter-branch.)\n\n 1. [Clean separation] Avoid confusing users (and prevent accidental\n re-pushing of old stuff) due to mixing old repo and rewritten\n repo together. (This is particularly a problem with filter-branch\n when using the --tag-name-filter option, and sometimes also an\n issue when only filtering a subset of branches.)\n\n 1. [Versatility] Provide the user the ability to extend the tool or\n even write new tools that leverage existing capabilities, and\n provide this extensibility in a way that (a) avoids the need to\n fork separate processes (which would destroy performance), (b)\n avoids making the user specify OS-dependent shell commands (which\n would prevent users from sharing commands with each other), (c)\n takes advantage of rich data structures (because hashes, dicts,\n lists, and arrays are prohibitively difficult in shell) and (d)\n provides reasonable string manipulation capabilities (which are\n sorely lacking in shell).\n\n 1. [Old commit references] Provide a way for users to use old commit\n IDs with the new repository (in particular via mapping from old to\n new hashes with refs/replace/ references).\n\n 1. [Commit message consistency] If commit messages refer to other\n commits by ID (e.g. \"this reverts commit 01234567890abcdef\", \"In\n commit 0013deadbeef9a...\"), those commit messages should be\n rewritten to refer to the new commit IDs.\n\n 1. [Become-empty pruning] Commits which become empty due to filtering\n should be pruned. If the parent of a commit is pruned, the first\n non-pruned ancestor needs to become the new parent. If no\n non-pruned ancestor exists and the commit was not a merge, then it\n becomes a new root commit. If no non-pruned ancestor exists and\n the commit was a merge, then the merge will have one less parent\n (and thus make it likely to become a non-merge commit which would\n itself be pruned if it had no file changes of its own). One\n special thing to note here is that we prune commits which become\n empty, NOT commits which start empty. Some projects intentionally\n create empty commits for versioning or publishing reasons, and\n these should not be removed. (As a special case, commits which\n started empty but whose parent was pruned away will also be\n considered to have \"become empty\".)\n\n 1. [Become-degenerate pruning] Pruning of commits which become empty\n can potentially cause topology changes, and there are lots of\n special cases. Normally, merge commits are not removed since they\n are needed to preserve the graph topology, but the pruning of\n parents and other ancestors can ultimately result in the loss of\n one or more parents. A simple case was already noted above: if a\n merge commit loses enough parents to become a non-merge commit and\n it has no file changes, then it too can be pruned. Merge commits\n can also have a topology that becomes degenerate: it could end up\n with the merge_base serving as both parents (if all intervening\n commits from the original repo were pruned), or it could end up\n with one parent which is an ancestor of its other parent. In such\n cases, if the merge has no file changes of its own, then the merge\n commit can also be pruned. However, much as we do with empty\n pruning we do not prune merge commits that started degenerate\n (which indicates it may have been intentional, such as with --no-ff\n merges) but only merge commits that become degenerate and have no\n file changes of their own.\n\n 1. [Speed] Filtering should be reasonably fast\n\n# How do I contribute?\n\nSee the [contributing guidelines](Documentation/Contributing.md).\n\n# Is there a Code of Conduct?\n\nParticipants in the filter-repo community are expected to adhere to\nthe same standards as for the git project, so the [git Code of\nConduct](https://git.kernel.org/pub/scm/git/git.git/tree/CODE_OF_CONDUCT.md)\napplies.\n\n# Upstream Improvements\n\nWork on filter-repo and [its\npredecessor](https://public-inbox.org/git/51419b2c0904072035u1182b507o836a67ac308d32b9@mail.gmail.com/)\nhas also driven numerous improvements to fast-export and fast-import\n(and occasionally other commands) in core git, based on things\nfilter-repo needs to do its work:\n\n * git-2.48.0 (to be released Jan 2025)\n * [fast-import: disallow more path components](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=da91a90c2f)\n * [fast-import: disallow \".\" and \"..\" path components](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=4a2790a257)\n * [fast-import: avoid making replace refs point to themselves](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=5e904f1a4a)\n * git-2.28.0\n * [fast-import: add new --date-format=raw-permissive format](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=d42a2fb72f)\n * git-2.24.0\n * [fast-export: handle nested tags](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=941790d7de)\n * [t9350: add tests for tags of things other than a commit](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=8d7d33c1ce)\n * [fast-export: allow user to request tags be marked with --mark-tags](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=a1638cfe12)\n * [fast-export: add support for --import-marks-if-exists](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=208d69246e)\n * [fast-import: add support for new 'alias' command](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=b8f50e5b60)\n * [fast-import: allow tags to be identified by mark labels](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=f73b2aba05)\n * [fast-import: fix handling of deleted tags](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=3164e6bd24)\n * [fast-export: fix exporting a tag and nothing else](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=af2abd870b)\n * [git-fast-import.txt: clarify that multiple merge commits are allowed](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=d1387d3895)\n * git-2.23.0\n * [t9350: fix encoding test to actually test reencoding](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=32615ce762)\n * [fast-import: support 'encoding' commit header](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=3edfcc65fd)\n * [fast-export: avoid stripping encoding header if we cannot reencode](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=ccbfc96dc4)\n * [fast-export: differentiate between explicitly UTF-8 and implicitly\n UTF-8](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=57a8be2cb0)\n * [fast-export: do automatic reencoding of commit messages only if\n requested](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=e80001f8fd)\n * git-2.22.0\n * [log,diff-tree: add --combined-all-paths option](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=d76ce4f734)\n * [t9300: demonstrate bug with get-mark and empty orphan commits](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=62edbec7de)\n * [git-fast-import.txt: fix wording about where ls command can appear](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=a63c54a019)\n * [fast-import: check most prominent commands first](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=5056bb7646)\n * [fast-import: only allow cat-blob requests where it makes sense](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=7ffde293f2)\n * [fast-import: fix erroneous handling of get-mark with empty orphan\n commits](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=cf7b857a77)\n * [Honor core.precomposeUnicode in more places](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=8e712ef6fc)\n * git-2.21.0\n * [fast-export: convert sha1 to oid](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=843b9e6d48)\n * [git-fast-import.txt: fix documentation for --quiet option](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=f55c979b14)\n * [git-fast-export.txt: clarify misleading documentation about rev-list\n args](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=4532be7cba)\n * [fast-export: use value from correct enum](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=b93b81e799)\n * [fast-export: avoid dying when filtering by paths and old tags exist](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=1f30c904b3)\n * [fast-export: move commit rewriting logic into a function for reuse](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=f129c4275c)\n * [fast-export: when using paths, avoid corrupt stream with non-existent\n mark](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=cd13762d8f)\n * [fast-export: ensure we export requested refs](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=fdf31b6369)\n * [fast-export: add --reference-excluded-parents option](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=530ca19c02)\n * [fast-import: remove unmaintained duplicate documentation](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=25dd3e4889)\n * [fast-export: add a --show-original-ids option to show\n original names](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=a965bb3116)\n * [git-show-ref.txt: fix order of flags](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=bd8d6f0def)\n * git-2.20.0\n * [update-ref: fix type of update_flags variable to\n match its usage](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=e4c34855a2)\n * [update-ref: allow --no-deref with --stdin](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=d345e9fbe7)\n * git-1.7.3\n * [fast-export: Fix dropping of files with --import-marks and path\n limiting](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=4087a02e45)\n * [fast-export: Add a --full-tree option](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=7f40ab0916)\n * [fast-export: Fix output order of D/F changes](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=060df62422)\n * [fast-import: Improve robustness when D->F changes provided in wrong\n order](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=253fb5f889)\n * git-1.6.4:\n * [fast-export: Set revs.topo_order before calling setup_revisions](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=668f3aa776)\n * [fast-export: Omit tags that tag trees](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=02c48cd69b)\n * [fast-export: Make sure we show actual ref names instead of \"(null)\"](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=2374502c6c)\n * [fast-export: Do parent rewriting to avoid dropping relevant commits](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=32164131db)\n * [fast-export: Add a --tag-of-filtered-object option for newly\n dangling tags](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=2d8ad46919)\n * [Add new fast-export testcases](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=25e0ca5dd6)\n * [fast-export: Document the fact that git-rev-list arguments are\n accepted](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=8af15d282e)\n * git-1.6.3:\n * [git-filter-branch: avoid collisions with variables in eval'ed\n commands](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=d5b0c97d13)\n * [Correct missing SP characters in grammar comment at top of\n fast-import.c](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=98e1a4186a)\n * [fast-export: Avoid dropping files from commits](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=ebeec7dbc5)\n * git-1.6.1.4:\n * [fast-export: ensure we traverse commits in topological order](\n https://git.kernel.org/pub/scm/git/git.git/commit/?id=784f8affe4)\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Quickly rewrite git repository history",
"version": "2.47.0",
"project_urls": {
"Homepage": "https://github.com/newren/git-filter-repo",
"Issues": "https://github.com/newren/git-filter-repo/issues/",
"Source": "https://github.com/newren/git-filter-repo"
},
"split_keywords": [],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "6060d3943f0880ebcb7e0bdf79254d10dddd39c7b656eeecae32b8806ff66dec",
"md5": "b758bf94e14d964d45d889671a2028eb",
"sha256": "2cd04929b9024e83e65db571cbe36aec65ead0cb5f9ec5abe42158654af5ad83"
},
"downloads": -1,
"filename": "git_filter_repo-2.47.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "b758bf94e14d964d45d889671a2028eb",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 76282,
"upload_time": "2024-12-04T03:10:46",
"upload_time_iso_8601": "2024-12-04T03:10:46.064932Z",
"url": "https://files.pythonhosted.org/packages/60/60/d3943f0880ebcb7e0bdf79254d10dddd39c7b656eeecae32b8806ff66dec/git_filter_repo-2.47.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "b9bb7a283f568af6b0528ade65e8ace84bd6ba46003e429101bcd62c232d01a5",
"md5": "9aa3e5b4a036bdbacaf59770b8ca40a4",
"sha256": "411b27e68a080c07a69c233cb526dbc2d848b09a72f10477f4444dd0822cf290"
},
"downloads": -1,
"filename": "git_filter_repo-2.47.0.tar.gz",
"has_sig": false,
"md5_digest": "9aa3e5b4a036bdbacaf59770b8ca40a4",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 275743,
"upload_time": "2024-12-04T03:10:48",
"upload_time_iso_8601": "2024-12-04T03:10:48.200717Z",
"url": "https://files.pythonhosted.org/packages/b9/bb/7a283f568af6b0528ade65e8ace84bd6ba46003e429101bcd62c232d01a5/git_filter_repo-2.47.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-04 03:10:48",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "newren",
"github_project": "git-filter-repo",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "git-filter-repo"
}
