The recommended git tool is: git
Cloning the remote Git repository
Cloning repository https://github.com/larson-group/sam_clubb.git
> git init /home/jenkins/workspace/sam_micro_drizzle_intel_test # timeout=10
Fetching upstream changes from https://github.com/larson-group/sam_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/sam_clubb.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/larson-group/sam_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 e9900c9df68eded64456193d48a2f1e113bf6b0e (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f e9900c9df68eded64456193d48a2f1e113bf6b0e # timeout=10
Commit message: "Autoupdated CLUBB_core Commit 573dc6073eb8dea603e3e6ba00111787bb750995 Author: bmg929 Date: Sat Apr 13 10:25:41 2024 -0500 I am committing a stats change to the ghost point values of zt stats output variables found in the monotonic flux limiter. These values are all being set simply to 0 at the ghost point for purposes of providing an easy comparison to stats output files from the clubb_ghost_exorcism branch. The code change is not at all answer changing. However, it is technically BIT_CHANGING."
> git rev-list --no-walk 4bb7aef9d9d4d53098862bfa03df016ed1697bad # timeout=10