forked from git/git
-
Notifications
You must be signed in to change notification settings - Fork 157
doc: convert git-stash, git tag and git worktree to synopis style #1969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
+280
−253
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,28 @@ | ||
stash.index:: | ||
ifndef::git-stash[] | ||
:see-show: See the description of the 'show' command in linkgit:git-stash[1]. | ||
endif::git-stash[] | ||
|
||
ifdef::git-stash[] | ||
:see-show: | ||
endif::git-stash[] | ||
|
||
`stash.index`:: | ||
If this is set to true, `git stash apply` and `git stash pop` will | ||
behave as if `--index` was supplied. Defaults to false. See the | ||
descriptions in linkgit:git-stash[1]. | ||
behave as if `--index` was supplied. Defaults to false. | ||
ifndef::git-stash[] | ||
See the descriptions in linkgit:git-stash[1]. | ||
endif::git-stash[] | ||
|
||
stash.showIncludeUntracked:: | ||
`stash.showIncludeUntracked`:: | ||
If this is set to true, the `git stash show` command will show | ||
the untracked files of a stash entry. Defaults to false. See | ||
the description of the 'show' command in linkgit:git-stash[1]. | ||
the untracked files of a stash entry. Defaults to false. {see-show} | ||
|
||
stash.showPatch:: | ||
`stash.showPatch`:: | ||
If this is set to true, the `git stash show` command without an | ||
option will show the stash entry in patch form. Defaults to false. | ||
See the description of the 'show' command in linkgit:git-stash[1]. | ||
{see-show} | ||
|
||
stash.showStat:: | ||
`stash.showStat`:: | ||
If this is set to true, the `git stash show` command without an | ||
option will show a diffstat of the stash entry. Defaults to true. | ||
See the description of the 'show' command in linkgit:git-stash[1]. | ||
{see-show} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,17 +1,23 @@ | ||
tag.forceSignAnnotated:: | ||
`tag.forceSignAnnotated`:: | ||
A boolean to specify whether annotated tags created should be GPG signed. | ||
If `--annotate` is specified on the command line, it takes | ||
precedence over this option. | ||
|
||
tag.sort:: | ||
This variable controls the sort ordering of tags when displayed by | ||
linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the | ||
value of this variable will be used as the default. | ||
`tag.sort`:: | ||
ifdef::git-tag[] | ||
This variable controls the sort ordering of tags when displayed by `git-tag`. | ||
endif::git-tag[] | ||
ifndef::git-tag[] | ||
This variable controls the sort ordering of tags when displayed by | ||
linkgit:git-tag[1]. | ||
endif::git-tag[] | ||
Without the `--sort=<value>` option provided, the value of this variable will | ||
be used as the default. | ||
|
||
tag.gpgSign:: | ||
`tag.gpgSign`:: | ||
A boolean to specify whether all tags should be GPG signed. | ||
Use of this option when running in an automated script can | ||
result in a large number of tags being signed. It is therefore | ||
convenient to use an agent to avoid typing your gpg passphrase | ||
convenient to use an agent to avoid typing your GPG passphrase | ||
several times. Note that this option doesn't affect tag signing | ||
behavior enabled by "-u <keyid>" or "--local-user=<keyid>" options. | ||
behavior enabled by `-u <keyid>` or `--local-user=<keyid>` options. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,19 @@ | ||
worktree.guessRemote:: | ||
`worktree.guessRemote`:: | ||
If no branch is specified and neither `-b` nor `-B` nor | ||
`--detach` is used, then `git worktree add` defaults to | ||
creating a new branch from HEAD. If `worktree.guessRemote` is | ||
set to true, `worktree add` tries to find a remote-tracking | ||
branch whose name uniquely matches the new branch name. If | ||
such a branch exists, it is checked out and set as "upstream" | ||
for the new branch. If no such match can be found, it falls | ||
back to creating a new branch from the current HEAD. | ||
back to creating a new branch from the current `HEAD`. | ||
|
||
worktree.useRelativePaths:: | ||
Link worktrees using relative paths (when "true") or absolute | ||
paths (when "false"). This is particularly useful for setups | ||
`worktree.useRelativePaths`:: | ||
Link worktrees using relative paths (when "`true`") or absolute | ||
paths (when "`false`"). This is particularly useful for setups | ||
where the repository and worktrees may be moved between | ||
different locations or environments. Defaults to "false". | ||
different locations or environments. Defaults to "`false`". | ||
+ | ||
Note that setting `worktree.useRelativePaths` to "true" implies enabling the | ||
Note that setting `worktree.useRelativePaths` to "`true`" implies enabling the | ||
`extensions.relativeWorktrees` config (see linkgit:git-config[1]), | ||
thus making it incompatible with older versions of Git. |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the Git mailing list, "Kristoffer Haugsbakk" wrote (reply to this):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the Git mailing list, Jean-Noël Avila wrote (reply to this):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the Git mailing list, Junio C Hamano wrote (reply to this):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the Git mailing list, Jean-Noël AVILA wrote (reply to this):
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the Git mailing list, Junio C Hamano wrote (reply to this):