gitlab-release-note-generator icon indicating copy to clipboard operation
gitlab-release-note-generator copied to clipboard

Published 20 hours ago • verified publisher icon jk1z

Issues and merge requests appear on two consecutive releases

Open lcmen opened this issue 5 years ago • 3 comments

Hi! Thank you for this library! It's been really useful for us.

I have a quick question: is there a reason to use updated_at (updated_after / updater_before) for issues and MRs? In our case MR gets updated after it gets merged and sometimes the same MR appears on two consecutive releases. Any idea what could be the problem?

lcmen avatar May 28 '20 11:05 lcmen

having the same issue

filipeportes avatar Sep 04 '20 10:09 filipeportes

Oh I see.. I should've use closed_at for issues and merged_at for merge requests

jk1z avatar May 07 '22 08:05 jk1z

yea, part of reasons past me was using updated_at was because Gitlab API only supports query on updated_at attribute in both MR and Issues endpoint. To fix this I would have to do a local filter after I have retrieved the data.

jk1z avatar May 07 '22 08:05 jk1z