[fpc-devel] [RFC] Modernising the FPC Release Process -- Proposal for Review
n7800
n7800 at inbox.ru
Fri Apr 17 22:01:41 CEST 2026
>
> However, if you insist on using a local tool (command-line or not): no
> problem.
> gitlab cli (glab) exists already. You can use that to handle merge
> requests
> without ever touching the web interface.
>
> Gitlab is API first, so If this is your wish, I'll even write a lazarus UI
>
> tool or FPC command-line tool to create the MR, merge it, all in one go.
>
> If that makes your (and other people's) life easier or more comfortable in
> a MR-based
> workflow, I am prepared to do the work.
>
> It will not take me an hour to create it, even without AI.
You don't have to use «glab» or the «GitLab REST API» — y ou can create a MR directly through Git. I sometimes do this for simple MRs:
> git push -o merge_request.create ... HEAD
See docs: https://docs.gitlab.com/topics/git/commit/#push-options
Note that you can specify many options, including labels, milestone, and target branch. You can write a script (in «two lines») to create MRs, for example, for two branches at once.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20260417/5e6788d4/attachment.htm>
More information about the fpc-devel
mailing list