Gitlab Milestone Issues

[base698]

1. Milestone shows up on Forge issue.
2. Milestone shows as ^A or ^B
   
3. Open a Gitlab Issue with a Group Milestone

Gitlab allows Milestones are on Group as well as the repository. The relationship is for Gitlab is different than Github: Groups contain repositories/projects. Both Groups and Projects can have Milestones. It may help to change the data model in forge-sql to include a Group and allow Repositories and the Group to attach Milestones.

Please include a backtrace in your report. In most cases doing:

N/A

and then going through the steps again should result in a backtrace.

N/A

[base698]

@tarsius Was starting to look into this. I see the milestone table has a reference to repository. In Gitlab the milestones are part of a group. There doesn't appear to be a group table.

I would propose adding:

• foreign key on milestone for it's issues
• groups table that contains repositories and milestones

[tarsius]

I have decided against implementing support for this.

Milestones are not essential; it's okay if one occasionally has to use the web interface to perform milestone related stuff.

I also do not particularly like Gitlab. It's less problematic than Github, but while many parts are open source, it follows an open core strategy. I have to support Github because so many FOSS projects are hosted there. This is also true for Gitlab, but to a much smaller extend. Both have gone all in on "AI".

The time I safe by limiting support for Gitlab, I can instead invest in supporting Forgejo; which is fully FOSS, and not just for practical reasons, it's main purpose isn't to make someone filthy rich. Furthermore, Codeberg has taken a firm stance against slop.