doc: merge-tree: improve example script

• Provide a commit message in the example command.

  The command will hang since it is waiting for a commit message on
  stdin.  Which is usable but not straightforward enough since this is
  example code.
• Use `||` directly since that is more straightforward than checking the
  last exit status.

  Also use `echo` and `exit` since `die` is not defined.
• Expose variable declarations.

Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Kristoffer Haugsbakk 2024-10-09 18:53:45 +02:00 committed by Junio C Hamano
parent 4f71522dfb
commit c4b8fb6ef2
1 changed files with 9 additions and 3 deletions

View File

@ -211,9 +211,15 @@ linkgit:git-commit-tree[1], linkgit:git-write-tree[1],
linkgit:git-update-ref[1], and linkgit:git-mktag[1]. Thus, it can be linkgit:git-update-ref[1], and linkgit:git-mktag[1]. Thus, it can be
used as a part of a series of steps such as: used as a part of a series of steps such as:


NEWTREE=$(git merge-tree --write-tree $BRANCH1 $BRANCH2) vi message.txt
test $? -eq 0 || die "There were conflicts..." BRANCH1=refs/heads/test
NEWCOMMIT=$(git commit-tree $NEWTREE -p $BRANCH1 -p $BRANCH2) BRANCH2=main
NEWTREE=$(git merge-tree --write-tree $BRANCH1 $BRANCH2) || {
echo "There were conflicts..." 1>&2
exit 1
}
NEWCOMMIT=$(git commit-tree $NEWTREE -F message.txt \
-p $BRANCH1 -p $BRANCH2)
git update-ref $BRANCH1 $NEWCOMMIT git update-ref $BRANCH1 $NEWCOMMIT


Note that when the exit status is non-zero, `NEWTREE` in this sequence Note that when the exit status is non-zero, `NEWTREE` in this sequence