Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redmine Pull request disappears #27

Open
calvu opened this issue Jun 18, 2020 · 4 comments
Open

Redmine Pull request disappears #27

calvu opened this issue Jun 18, 2020 · 4 comments

Comments

@calvu
Copy link

calvu commented Jun 18, 2020

Hello,

My setup:

  • Redmine 3.4.13 (also tested with 3.4.6)
  • Gitea 1.11.6
  • Plugin v2.22

Problem:
Creating a pullrequest with the ticket number "#1234" within Gitea creates an entry in the Redmine Ticket.
As soon as the pullrequest is closed, by Merge or Close, the entry disappears in the ticket.
I have already looked at the Redmine DB and noticed the following behavior.

  • When a pull request is created, "merge_requests" and "issues_merge_requests" creates the corresponding entries in the table.
  • When merging a pull request, the entry is deleted from the "issues_merge_requests" table and no new one is created.

Greetings,
Peter

@tf
Copy link
Owner

tf commented Jun 23, 2020

Maybe the webhook sent on close does not contain the description/body? Every time that is changed, the linked merge requests are updated.

I'm not using the Gitea integration myself. So I can only guess. Maybe @saitho who developed the adapter has more ideas?

@jpraet
Copy link
Contributor

jpraet commented May 27, 2021

I am experiencing the same issue. Indeed the body is empty in gitea's PR merged/closed webhook payload.

@tf
Copy link
Owner

tf commented May 27, 2021

Maybe we can make the Gitea adater only update the description if the corresponding field is present? Happy to accept a PR that adds a test case similar to the existing ones with a webhook payload that represents this case and makes sure.

@jpraet
Copy link
Contributor

jpraet commented May 31, 2021

It will be fixed on the Gitea side in the upcoming 1.14.3 patch release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants