search

jk1z / gitlab-release-note-generator

A Gitlab release note generator
MIT License
99 stars 37 forks source link

Issues and merge requests appear on two consecutive releases #27

Open lcmen opened 4 years ago

lcmen commented 4 years ago

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?

filipeportes commented 4 years ago

having the same issue

jk1z commented 2 years ago

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

jk1z commented 2 years ago

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.