# Issue with git commit - fatal: bad config variable 'gpg.format' in file '/home/581/ns3783/.gitconfig' at line 10

**URL:** <https://forum.access-hive.org.au/t/issue-with-git-commit-fatal-bad-config-variable-gpg-format-in-file-home-581-ns3783-gitconfig-at-line-10/582>\
**Category:** Technical\
**Tags:** github\
**Created:** [22 March 2023 01:36 UTC](https://forum.access-hive.org.au/t/issue-with-git-commit-fatal-bad-config-variable-gpg-format-in-file-home-581-ns3783-gitconfig-at-line-10/582 "2023-03-22T01:36:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ribeirosantosn](https://avatars.discourse-cdn.com/v4/letter/r/e495f1/32.png) [@ribeirosantosn](https://forum.access-hive.org.au/u/ribeirosantosn)\
**Post date:** [22 March 2023 01:36 UTC](https://forum.access-hive.org.au/t/issue-with-git-commit-fatal-bad-config-variable-gpg-format-in-file-home-581-ns3783-gitconfig-at-line-10/582/1 "2023-03-22T01:36:05Z")

</div>

I am having an issue with git commit.

I cloned a repo into my g/data folder but am not being able to commit to it :  
error: unsupported value for gpg.format: ssh  
fatal: bad config variable ‘gpg.format’ in file ‘/home/581/ns3783/.gitconfig’ at line 10

The line is question is the format =ssh and I checked and the version of git I have on gadi doesn’t support ssh. I don’t seem to be able to update the version.

Did someone encounter this problem before? What was your solution?

Thank you!

---

<div class="post-metadata">

**Author:** ![Aidan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aidan/32/42_2.png) [@Aidan](https://forum.access-hive.org.au/u/Aidan)\
**Post date:** [22 March 2023 01:58 UTC](https://forum.access-hive.org.au/t/issue-with-git-commit-fatal-bad-config-variable-gpg-format-in-file-home-581-ns3783-gitconfig-at-line-10/582/2 "2023-03-22T01:58:38Z")

</div>

Hi @ribeirosantosn,

Note that this allows for [signing commits](https://withblue.ink/2020/05/17/how-and-why-to-sign-git-commits.html) which is a good idea.

The easiest way to get around this is to use the [`hh5` conda environment](http://climate-cms.wikis.unsw.edu.au/Conda#Conda_Python_Environments) as it has a new enough version of `git`

```bash
$ which git
/g/data3/hh5/public/apps/miniconda3/envs/analysis3-23.01/bin/git
$ git --version
git version 2.39.1

```

Note that [git v2.3.4 or greater is required](https://blog.dbrgn.ch/2021/11/16/git-ssh-signatures/).

There are also newer versions of `git` available in the system modules:

```auto
$ module avail git
----------------------------------------------------------------- /apps/Modules/modulefiles -----------------------------------------------------------------
git/2.24.1 git/2.37.3 git/2.39.1 git/2.39.2  

```

and though they should work (and I just tested and they seemed to), I’ve sometimes still had issues that I haven’t taken the time to track down.

You also have the option of removing the relevant lines from your `.gitconfig`:

```auto
[commit]
        gpgsign = true
[gpg]
        format = ssh

```

---

<div class="post-metadata">

**Author:** ![ribeirosantosn](https://avatars.discourse-cdn.com/v4/letter/r/e495f1/32.png) [@ribeirosantosn](https://forum.access-hive.org.au/u/ribeirosantosn)\
**Post date:** [22 March 2023 02:19 UTC](https://forum.access-hive.org.au/t/issue-with-git-commit-fatal-bad-config-variable-gpg-format-in-file-home-581-ns3783-gitconfig-at-line-10/582/3 "2023-03-22T02:19:40Z")

</div>

Thank you. This solved the git version issue.

I ran into another issue afterwards:  
error: Couldn’t load public key id\_ed25519: No such file or directory?

In the end, I was required to remove those lines from my ~/.gitconfig to allow it to find the the correct location of the key.