Dashboard showing duplicate commits #3197

@andreymal commented on GitHub (Aug 15, 2019):

@‍stale still nope

@andreymal commented on GitHub (Aug 15, 2019): **@‍stale** still nope

GiteaMirror commented

@lunny commented on GitHub (Aug 15, 2019):

@andreymal @Akito13 could you test v1.9.1 fixed that? There is a bug duplicated webhooks fixed on v1.9.1 maybe it's related.

@lunny commented on GitHub (Aug 15, 2019): @andreymal @Akito13 could you test v1.9.1 fixed that? There is a bug duplicated webhooks fixed on v1.9.1 maybe it's related.

GiteaMirror commented

@andreymal commented on GitHub (Sep 23, 2019):

@lunny still present in v1.9.1 (didn't test v1.9.3 yet)

@andreymal commented on GitHub (Sep 23, 2019): @lunny still present in v1.9.1 (didn't test v1.9.3 yet) ![](https://i.imgur.com/EmcU6PC.png)

GiteaMirror commented

@lafriks commented on GitHub (Sep 23, 2019):

@andreymal old ones that was already duplicated won't go away. It should not happen anymore for new commits with latest version

@lafriks commented on GitHub (Sep 23, 2019): @andreymal old ones that was already duplicated won't go away. It should not happen anymore for new commits with latest version

GiteaMirror commented

@andreymal commented on GitHub (Sep 23, 2019):

@lafriks this is not old, this happened 6 days ago with gitea v1.9.1

@andreymal commented on GitHub (Sep 23, 2019): @lafriks this is not old, this happened 6 days ago with gitea v1.9.1

GiteaMirror commented

@andreymal commented on GitHub (Sep 23, 2019):

@lafriks tried v1.9.3 right now — still happens

@andreymal commented on GitHub (Sep 23, 2019): @lafriks tried v1.9.3 right now — still happens ![](https://i.imgur.com/2SKVCbT.png)

GiteaMirror commented

@guillep2k commented on GitHub (Sep 23, 2019):

@lafriks Could this problem be related to this? (follow the comment)

@guillep2k commented on GitHub (Sep 23, 2019): @lafriks Could this problem be related to [this](https://github.com/go-gitea/gitea/issues/7843#issuecomment-533966958)? (follow the comment)

GiteaMirror commented

@lafriks commented on GitHub (Sep 23, 2019):

Could be, hard to tell

@lafriks commented on GitHub (Sep 23, 2019): Could be, hard to tell

GiteaMirror commented

@lunny commented on GitHub (Sep 30, 2019):

Have you tried to Resynchronize pre-receive, update and post-receive hooks of all repositories. on your admin panel.

@lunny commented on GitHub (Sep 30, 2019): Have you tried to `Resynchronize pre-receive, update and post-receive hooks of all repositories.` on your admin panel.

GiteaMirror commented

@theAkito commented on GitHub (Nov 21, 2019):

Update 2019|22|21

Since a couple dozen commits to Gitea this issue happens all the time when commiting from the WebUI. No matter the conditions. It does not matter anymore, if other files are already open or not.

@theAkito commented on GitHub (Nov 21, 2019): ## Update 2019|22|21 Since a couple dozen commits to Gitea this issue happens all the time when commiting from the WebUI. No matter the conditions. It does not matter anymore, if other files are already open or not.

GiteaMirror commented

@zeripath commented on GitHub (Nov 21, 2019):

What version of Gitea? Could you try on 1.10?

Just double check that you haven't got two Gitea hooks in your Gitea repositories?

@zeripath commented on GitHub (Nov 21, 2019): What version of Gitea? Could you try on 1.10? Just double check that you haven't got two Gitea hooks in your Gitea repositories?

GiteaMirror commented

@theAkito commented on GitHub (Nov 21, 2019):

@zeripath

Since a couple dozen commits to Gitea

As in I used a couple of the most recent versions of Gitea from the past weeks.

I also did not set up any Hooks manually. Even so, I still checked and I don't see any duplicate hooks.

@theAkito commented on GitHub (Nov 21, 2019): @zeripath > Since a couple dozen commits to Gitea As in I used a couple of the most recent versions of Gitea from the past weeks. I also did not set up any Hooks manually. Even so, I still checked and I don't see any duplicate hooks.

GiteaMirror commented

@guillep2k commented on GitHub (Nov 22, 2019):

@zeripath check my comment here. I think this may be the cause.

@guillep2k commented on GitHub (Nov 22, 2019): @zeripath check [my comment here](https://github.com/go-gitea/gitea/issues/7843#issuecomment-533966958). I think this may be the cause.

GiteaMirror commented

@4oo4 commented on GitHub (Feb 23, 2020):

I'm still having this with v1.11.1, I just noticed that somehow I have duplicate hooks scripts on my Gitea server.

/home/git/gitea-repositories/user/my-repo.git/hooks $ ls post-receive.d
gitea  post-receive

/home/git/gitea-repositories/user/my-repo.git/hooks > $ cat post-receive.d/*
#!/usr/bin/env bash
"/home/git/gitea/gitea" hook --config='/home/git/gitea/custom/conf/app.ini' post-receive
#!/usr/bin/env bash
"/home/git/gitea/gitea" hook --config='/home/git/gitea/custom/conf/app.ini' post-receive

Not sure how that happened but I'm guessing that removing one of those in all of my repos will fix it. I think I had to do this before when migrating from Gogs, not sure when these hooks got duplicated.

@4oo4 commented on GitHub (Feb 23, 2020): I'm still having this with v1.11.1, I just noticed that somehow I have duplicate hooks scripts on my Gitea server. ```bash /home/git/gitea-repositories/user/my-repo.git/hooks $ ls post-receive.d gitea post-receive /home/git/gitea-repositories/user/my-repo.git/hooks > $ cat post-receive.d/* #!/usr/bin/env bash "/home/git/gitea/gitea" hook --config='/home/git/gitea/custom/conf/app.ini' post-receive #!/usr/bin/env bash "/home/git/gitea/gitea" hook --config='/home/git/gitea/custom/conf/app.ini' post-receive ``` Not sure how that happened but I'm guessing that removing one of those in all of my repos will fix it. I think I had to do this before when migrating from Gogs, not sure when these hooks got duplicated.

GiteaMirror commented

@theAkito commented on GitHub (Feb 23, 2020):

@4oo4 Post your results, when you are done applying the possible fix.

@theAkito commented on GitHub (Feb 23, 2020): @4oo4 Post your results, when you are done applying the possible fix.

GiteaMirror commented

@guillep2k commented on GitHub (Feb 24, 2020):

The good ones are those named gitea. You should have:

$ find hooks ! -name '*.sample' -type f
hooks/pre-receive.d/gitea     // Gitea's pre-receive hook
hooks/pre-receive             // Cycles through hooks inside hooks/pre-receive.d/
hooks/update.d/gitea          // Gitea's update hook
hooks/update                  // Cycles through hooks inside hooks/update.d/
hooks/post-receive.d/gitea    // Gitea's post-receive hook
hooks/post-receive            // Cycles through hooks inside hooks/post-receive.d/

(You can ignore the .sample hooks, which have no effect).

Please be aware that there could also be some other hooks placed by repository owners as long as you enabled them.

@guillep2k commented on GitHub (Feb 24, 2020): The good ones are those named `gitea`. You should have: ``` $ find hooks ! -name '*.sample' -type f hooks/pre-receive.d/gitea // Gitea's pre-receive hook hooks/pre-receive // Cycles through hooks inside hooks/pre-receive.d/ hooks/update.d/gitea // Gitea's update hook hooks/update // Cycles through hooks inside hooks/update.d/ hooks/post-receive.d/gitea // Gitea's post-receive hook hooks/post-receive // Cycles through hooks inside hooks/post-receive.d/ ``` (You can ignore the `.sample` hooks, which have no effect). Please be aware that there could also be some other hooks placed by repository owners as long as you enabled them.

GiteaMirror commented

@4oo4 commented on GitHub (Feb 24, 2020):

@theAkito That fixed it for me. Basically in my hooks/pre-receive.d and hooks/post-receive.d folders in each repo, there was a duplicate post-recieve or pre-receive hook, and like @guillep2k says I kept the ones named gitea as the good ones.

To fix them en masse, first cd to your folder where you store your gitea repositories. Then this one liner will find those duplicates and get rid of them while keeping the good ones. not sure what that would do for custom user hooks though, could those possibly be named either pre-receive or post-receive?

find . -regextype egrep -regex ".*/*.git/hooks/(pre|post)-receive.d/(pre|post)-receive" -exec sudo rm {} \;

Obviously you want to back up your repositories directory before running that. Then, when I committed to a repo that had the duplicate hooks, it only displayed once in the dashboard. I didn't realize it until now but for a while the duplicate ones were also giving me duplicate messages in the terminal when I ran git push to sync my repos. That's fixed now too.

@4oo4 commented on GitHub (Feb 24, 2020): @theAkito That fixed it for me. Basically in my `hooks/pre-receive.d` and `hooks/post-receive.d` folders in each repo, there was a duplicate `post-recieve` or `pre-receive` hook, and like @guillep2k says I kept the ones named `gitea` as the good ones. To fix them en masse, first `cd` to your folder where you store your gitea repositories. Then this one liner will find those duplicates and get rid of them while keeping the good ones. not sure what that would do for custom user hooks though, could those possibly be named either `pre-receive` or `post-receive`? `find . -regextype egrep -regex ".*/*.git/hooks/(pre|post)-receive.d/(pre|post)-receive" -exec sudo rm {} \;` Obviously you want to back up your repositories directory before running that. Then, when I committed to a repo that had the duplicate hooks, it only displayed once in the dashboard. I didn't realize it until now but for a while the duplicate ones were also giving me duplicate messages in the terminal when I ran `git push` to sync my repos. That's fixed now too.

GiteaMirror commented