mirror of
https://github.com/git-for-windows/git.git
synced 2026-06-18 21:25:03 -05:00
7d6f98431e
Add a "rename" subcommand to git-refs(1) with the syntax: $ git refs rename <oldref> <newref> It renames <oldref> together with its reflog to <newref>; even when used on a local branch ref, the current value and the reflog of the ref are the only things that are renamed. Document it and redirect casual users to "git branch -m" if that is what they wanted to do. Co-authored-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
151 lines
4.8 KiB
Plaintext
151 lines
4.8 KiB
Plaintext
git-refs(1)
|
|
===========
|
|
|
|
NAME
|
|
----
|
|
git-refs - Low-level access to refs
|
|
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[synopsis]
|
|
git refs migrate --ref-format=<format> [--no-reflog] [--dry-run]
|
|
git refs verify [--strict] [--verbose]
|
|
git refs list [--count=<count>] [--shell|--perl|--python|--tcl]
|
|
[(--sort=<key>)...] [--format=<format>]
|
|
[--include-root-refs] [--points-at=<object>]
|
|
[--merged[=<object>]] [--no-merged[=<object>]]
|
|
[--contains[=<object>]] [--no-contains[=<object>]]
|
|
[(--exclude=<pattern>)...] [--start-after=<marker>]
|
|
[ --stdin | (<pattern>...)]
|
|
git refs exists <ref>
|
|
git refs optimize [--all] [--no-prune] [--auto] [--include <pattern>] [--exclude <pattern>]
|
|
git refs create [--message=<reason>] [--no-deref] [--create-reflog] <ref> <new-value>
|
|
git refs delete [--message=<reason>] [--no-deref] <ref> [<old-value>]
|
|
git refs update [--message=<reason>] [--no-deref] [--create-reflog] <ref> <new-value> [<old-value>]
|
|
git refs rename [--message=<reason>] <old-ref> <new-ref>
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
|
|
This command provides low-level access to refs.
|
|
|
|
COMMANDS
|
|
--------
|
|
|
|
`migrate`::
|
|
Migrate ref store between different formats.
|
|
|
|
`verify`::
|
|
Verify reference database consistency.
|
|
|
|
list::
|
|
List references in the repository with support for filtering,
|
|
formatting, and sorting. This subcommand is an alias for
|
|
linkgit:git-for-each-ref[1] and offers identical functionality.
|
|
|
|
exists::
|
|
Check whether the given reference exists. Returns an exit code of 0 if
|
|
it does, 2 if it is missing, and 1 in case looking up the reference
|
|
failed with an error other than the reference being missing. This does
|
|
not verify whether the reference resolves to an actual object.
|
|
|
|
optimize::
|
|
Optimizes references to improve repository performance and reduce disk
|
|
usage. This subcommand is an alias for linkgit:git-pack-refs[1] and
|
|
offers identical functionality.
|
|
|
|
create::
|
|
Create the given reference, which must not already exist, pointing at
|
|
`<new-value>`.
|
|
|
|
delete::
|
|
Delete the given reference. This subcommand mirrors `git update-ref -d`
|
|
(see linkgit:git-update-ref[1]). When `<old-value>` is given, the
|
|
reference is only deleted after verifying that it currently contains
|
|
`<old-value>`.
|
|
|
|
update::
|
|
Update the given reference to point at `<new-value>`. If `<old-value>`
|
|
is given, the reference is only updated after verifying that it
|
|
currently contains `<old-value>`. As a special case, an all-zeroes
|
|
`<new-value>` deletes the branch, whereas an all-zeroes `<old-value>`
|
|
ensures that the branch does not yet exist.
|
|
|
|
rename::
|
|
Rename the reference `<oldref>` to `<newref>`. The old reference must
|
|
exist and the new reference must not yet exist, and both must have a
|
|
well-formed name (see linkgit:git-check-ref-format[1]).
|
|
|
|
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:
|
|
+
|
|
include::ref-storage-format.adoc[]
|
|
|
|
`--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.
|
|
|
|
`--reflog`::
|
|
`--no-reflog`::
|
|
Choose between migrating the reflog data to the new backend,
|
|
and discarding them. The default is "--reflog", to migrate.
|
|
|
|
The following options are specific to `git refs verify`:
|
|
|
|
`--strict`::
|
|
Enable stricter error checking. This will cause warnings to be
|
|
reported as errors. See linkgit:git-fsck[1].
|
|
|
|
`--verbose`::
|
|
When verifying the reference database consistency, be chatty.
|
|
|
|
The following options are specific to 'git refs list':
|
|
|
|
include::for-each-ref-options.adoc[]
|
|
|
|
The following options are specific to 'git refs optimize':
|
|
|
|
include::pack-refs-options.adoc[]
|
|
|
|
The following options are specific to commands which write references:
|
|
|
|
`--create-reflog`::
|
|
Create a reflog for the reference even if one would not ordinarily be
|
|
created.
|
|
|
|
`--message=<reason>`::
|
|
Use the given <reason> string for the reflog entry associated with the
|
|
update. An empty message is rejected.
|
|
|
|
`--no-deref`::
|
|
Operate on <ref> itself rather than the reference it points to via a
|
|
symbolic ref.
|
|
|
|
KNOWN LIMITATIONS
|
|
-----------------
|
|
|
|
The ref format migration has several known limitations in its current form:
|
|
|
|
* 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 linkgit:git[1] suite
|