MRs not showing up in inactive reports due to the missed milestone labels being applied
I was doing some MR triaging and noticed a few MRs that were not being picked up by the "Inactive community MRs" script because the GitLab bot was updating the milestone every month which counted as an activity
gitlab-org/gitlab!24359 (closed) gitlab-org/gitlab!55691 (closed) gitlab-org/gitlab!57977 (closed)
Proposal
There are three possible proposals I can think of. I've listed them below in order of decreasing complexity and usefulness.
- We find a way to ignore the moving milestone and application of the missed milestone label when determining inactivity.
- We stop the bot from auto moving the milestone on Community contribution in triage-reports MRs
- We make it policy not to have release milestones on Community contribution in triage-reports MRs
Edited by Sam Beckham