The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/clubb.git
> git init /home/jenkins/workspace/clubb_api_commitment_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/clubb.git
> git --version # timeout=10
> git --version # 'git version 2.34.1'
using GIT_ASKPASS to set credentials A token based key used by Jenkins to preform Github actions, created 6/21/2021
> git fetch --tags --force --progress -- https://github.com/larson-group/clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/larson-group/clubb.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision e904e3ffbf83888681ba64f9008890329bd18631 (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f e904e3ffbf83888681ba64f9008890329bd18631 # timeout=10
Commit message: "Fixing bug. RESOLVED:556370c6406e6b943b88affbe7728a5036b1ba22, this was catchable by using debugging flags, but seems to otherwise cause no issues. Investigating I found that it only clips the below ground level, so that must not have been affecting other levels. This is technically BIT_CHANGING since it resolves an issue."
> git rev-list --no-walk 7b429b2f394be33db0348d15755e28d832264e07 # timeout=10