Push success but display an error log

[lunny]

Don't know how to reproduce that, maybe some special commit message and I'm finding it.

core git:(master) git push origin master
Counting objects: 4, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 1.83 KiB | 0 bytes/s, done.
Total 4 (delta 1), reused 0 (delta 0)
remote: 2017/03/03 22:17:40 [...tea/models/update.go:147 PushUpdate()] [E] updateIssuesCommit: No issue number specified
To http://192.168.0.103:3000/lunny/core.git
   8e2e75f..c0ba85e  master -> master

[tboerger]

Maybe some fixes #number message?

[lunny]

Maybe, but I have tried many times, cannot reproduce it. Confusing.

[lunny]

Move this to v1.1 since cannot reproduce.

[willemvd]

Just happened to me after pushing with --mirror from a bare repository on my machine to a brand new repo on a brand new installing of docker 1.1.0

[mjwwit]

Just happened here as well after pushing with --follow-tags. At first I thought it was because of a commit message, but after reading these comments it seems it is totally random...

[pmattern]

At least to some degree the problem seems to depend on some property of the repository in question. I can reproduce 100% here with 03d7998 and github.com/palinek/nm-tray on an Arch Linux as follows:

• Install a Gitea instance from scratch. Minimal handling, so no further tweaking after the installer is finished.
• Have an arbitrary non-administrative user create a repository "nm-tray" in his own account (so not belonging to some other organization).
• Have the user clone the repository on the command line git clone https://github.com/palinek/nm-tray.git
• Add the Gitea instance as additional remote git remote add foo http://<HTTP URL as provided by the Gitea UI>.
• Have the user populate the repository by running git push -u foo master when it was not initialized by Gitea or git push --force foo master when it was.

[pmattern]

Indeed the problem does not seem to be fully solved yet. Running 0693fbf I cannot see it any longer with nm-tray (and a bunch of others either), but it still exists in FeatherNotes or lxqt-session, same steps as in my previous comment.

EDIT Add another repository that's still affected.

[lunny]

@pmattern I see so I reopened it. #1220 did not resolve it completely.