Gitea pull request handling is inconsistent

[xoxys]

If a pull request is not closed and a change was commited to the referending branch the commit will be appended to the existing pull request. But the drone status for this commit does not exist in the pr:

Forked repo:

Pull request:

Also drone does not run again if a opened pull request was updated with another commit. Is it possible to re-run drone if there was a new commit to a pull request (pull request updated)?

[tboerger]

If drone receives a webhook it will start another build.

[xoxys]

@tboerger How does this solve my described problem?

[pylanglois]

I have the same problem with gitea/drone

It seems that gitea does not have all the webhooks implemented (go-gitea/gitea#2418). Maybe this is a part of the problem.

Gitea does not display the PR state correctly. Only the first commit carries the state from the drone build. It is misleading because drone will build all the pull request, not the specific commit "54acdb3536" in your case. Every PR rebuild will update the state of the first commit in gitea. As a workaround, you can go in drone web interface and manually rebuild the pull request, it will rebuild all commit related to that PR.

The state of the build should be seen in the PR title, not on the "first commit" since each commit as a different state. Probably a gitea issue...

[xoxys]

Any chance to get this fixed?

[bradrydzewski]

This is not on my current priority list, so I would recommend sending a pull request if you would like to see this resolved in a timely matter.

[tboerger]

/cc @appleboy @lunny

[xoxys]

@tboerger Thanks for pointing this to gitea

[xoxys]

@bradrydzewski Thanks for your reply. I'm not a developer so for me its hard to address this issue

[bradrydzewski]

fixed in 1.0