Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.47.0 10/06/24
- 2.46.1 → 2.46.2 no changes
- 2.46.0 07/29/24
OPTIONS
The following options are specific to git refs migrate:
- --ref-format=<format>
-
The ref format to migrate the ref store to. Can be one of:
-
files
for loose files with packed-refs. This is the default. -
reftable
for the reftable format. This format is experimental and its internals are subject to change.
-
- --dry-run
-
Perform the migration, but do not modify the repository. The migrated refs will be written into a separate directory that can be inspected separately. The name of the directory will be reported on stdout. This can be used to double check that the migration works as expected before performing the actual migration.
KNOWN LIMITATIONS
The ref format migration has several known limitations in its current form:
-
It is not possible to migrate repositories that have reflogs.
-
It is not possible to migrate repositories that have worktrees.
-
There is no way to block concurrent writes to the repository during an ongoing migration. Concurrent writes can lead to an inconsistent migrated state. Users are expected to block writes on a higher level. If your repository is registered for scheduled maintenance, it is recommended to unregister it first with git-maintenance(1).
These limitations may eventually be lifted.
GIT
Part of the git[1] suite