# \[SOLVED\] How to close an issue with a commit + push?

**URL:** <https://forum.gitea.com/t/solved-how-to-close-an-issue-with-a-commit-push/604>\
**Category:** Gitea Usages\
**Created:** [October 11, 2018, 12:59pm UTC](https://forum.gitea.com/t/solved-how-to-close-an-issue-with-a-commit-push/604 "2018-10-11T12:59:06Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![pcopissa](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/pcopissa/32/276_2.png) [@pcopissa](https://forum.gitea.com/u/pcopissa)\
**Post date:** [October 18, 2018, 9:24am UTC](https://forum.gitea.com/t/solved-how-to-close-an-issue-with-a-commit-push/604/25 "2018-10-18T09:24:42Z")

</div>

Ok, I think I have made some progress:

I created an account on `try.gitea.io` + repository + one issue (#1).  
I tried to clone the repository via SSH in GitExtension GUI, specifying URL `pcopissa@try.gitea.io:pcopissa/test.git`. This failed with:  
`FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)`  
`fatal: Could not read from remote repository.`

I then tried to clone the repository via HTTPS, which also failed with GitExtension Windows GUI client.(this time it complained about not finding a few DLLs and even when copied over, complained about some missing entry points)  
I therefore cloned the repository via MSYS2 `git.exe` CLI. Specifically:  
`git clone 'https://try.gitea.io/pcopissa/test.git'`  
I committed + pushed with the usual three line commit message mentionned above ad nauseam (with `fixes #1` as the third line)  
**This closed the issue.**

The most significant difference here is the protocol: In all the tests mentionned above, I have used SSH + GitExtension with URL `git@git.lan:p.copissa/test`. And that worked (in the sense, I could clone, commit, push, but closing issues would fail)

So I tried using HTTPS and MSYS2 `git.exe`. Specifically:  
`git clone http://git.lan:3000/p.copissa/test.git`  
I then commited + pushed with the above-mentionned commit message.  
**The issue got closed.**

Then I tried with SSH and the same MSYS2 `git.exe` (needed to `export GIT_SSH` environment to make that work with Putty’s `plink.exe` instead of `ssh`). Specifically:  
`git clone 'git@git.lan:p.copissa/test'`  
Then committed + pushed as above.  
**The issue remained open.**

I have tried to create a Gitea user `git` and added it as a collaborator, specifying `git` as the committer.  
None of this allowed to close the issue via commit over SSH.

Note that when pushing via HTTP, `git.exe` paused to asked me for a username and password. (Apparently this has to be a Gitea user). On the over hand, `git.exe` never paused when committing over SSH.

So at this point it seems it has something to do with using SSH.

This is on Gitea 1.5.2 (release) BTW.

---

_[View the full topic](https://forum.gitea.com/t/solved-how-to-close-an-issue-with-a-commit-push/604)._