How does sharness deal with git configuration?

[mcepl]

I have written this testing script:

#!/bin/sh


test_description='git fixup

Testing selection of commits for git commit --fixup
'

TEST_PASSES_SANITIZE_LEAK=true

. ../sharness/sharness.sh

test_expect_success 'setup' '
    git init almost-complete &&
    cd almost-complete/ &&
    echo "Testing file 1" >test_01.txt &&
    git add test_01.txt &&
    git commit -m "Commiting the first file." &&
    echo "Testing file 2" >test_02.txt &&
    git add test_02.txt  &&
    git commit -m "Commiting the second file." &&
    echo "Modifying the first file." >>test_01.txt  &&
    git add test_01.txt  &&
    ./git-fixup.sh --no-commit --fixup >out &&
    test_grep "Commiting the first file." out
'

test_done

but the result is very bad:

mitmanek:t (git-request-get-merge *%) $ ./t7650-fixup.t -d -v
expecting success: 
    git init almost-complete &&
    cd almost-complete/ &&
    echo "Testing file 1" >test_01.txt &&
    git add test_01.txt &&
    git commit -m "Commiting the first file." &&
    echo "Testing file 2" >test_02.txt &&
    git add test_02.txt  &&
    git commit -m "Commiting the second file." &&
    echo "Modifying the first file." >>test_01.txt  &&
    git add test_01.txt  &&
    ./git-fixup.sh --no-commit --fixup >out &&
    test_grep "Commiting the first file." out

hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
Initialized empty Git repository in /home/matej/archiv/2024/projekty/hlupak/t/trash directory.t7650-fixup/almost-complete/.git/
Author identity unknown

*** Please tell me who you are.

Run

  git config --global user.email "[email protected]"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident name (for <[email protected]>) not allowed
not ok 1 - setup
#	
#	   git init almost-complete &&
#	   cd almost-complete/ &&
#	   echo "Testing file 1" >test_01.txt &&
#	   git add test_01.txt &&
#	   git commit -m "Commiting the first file." &&
#	   echo "Testing file 2" >test_02.txt &&
#	   git add test_02.txt  &&
#	   git commit -m "Commiting the second file." &&
#	   echo "Modifying the first file." >>test_01.txt  &&
#	   git add test_01.txt  &&
#	   ./git-fixup.sh --no-commit --fixup >out &&
#	   test_grep "Commiting the first file." out
#	

# failed 1 among 1 test(s)
1..1
mitmanek:t (git-request-get-merge *%) $ 

How does sharness deal with the Git configuration, particularly options user.email and user.name? Should I put some config file somewhere?

[felipec]

@mcepl it's explained in the intro on the README: the $HOME variable is set to a temporary directory. Git expects the configuration in ~/.gitconfig, so you can create that file with a barebones config.

But what I do in my git tests is include a test-lib.sh file that contains the following:

[email protected]
GIT_AUTHOR_NAME='A U Thor'
[email protected]
GIT_COMMITTER_NAME='C O Mitter'
export GIT_AUTHOR_EMAIL GIT_AUTHOR_NAME
export GIT_COMMITTER_EMAIL GIT_COMMITTER_NAME

This is similar to what git.git does. That way there's no need to create a config file and git doesn't complain about not having an identity.