[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFE] Migration to gitlab

From: Alex Gramiak
Subject: Re: [RFE] Migration to gitlab
Date: Thu, 25 Apr 2019 07:45:42 -0600
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)

Toon Claes <address@hidden> writes:

> Alex Gramiak <address@hidden> writes:
>> Is there an API to get the template for MRs or issues? If so, then Emacs
>> could use it in report-emacs-bug (or a more general report-emacs-issue)
>> and a new emacs-create-merge-request.
> You can definitely create MRs or issues through the API. I'm not sure
> about getting the template, but I don't see much added value to have
> this feature cause you can put the template in emacs itself.

Getting the template would allow for avoiding duplication between the
Emacs side and the Gitlab side, no? In general, it would allow for
3rd-party tools to provide a better (more complete/equivalent)
experience for creating Gitlab issues/MRs.

>> https://github.com/magit/ghub (despite the name, it supports Gitlab and
>> other "forges") should be mentioned in this discussion, though it's not
>> currently in ELPA.
> Magit is a awesome package, and recent the support for "forges" is
> great, although not yet very mature. But I usually don't see people here
> talk about magit, they tend to use the built-in vc-git instead. So I'm
> not sure we can rely on magit or vc-git should get also support for
> forges...

I agree that it shouldn't depend on Magit, but ghub at least doesn't
depend on it. It's https://github.com/magit/forge that depends on Magit.

I don't know enough about the Gitlab API to know whether it's worth it
to leverage ghub (and get it copyright-assigned and into ELPA) rather
than to roll our own in a hypothetical gitlab.el.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]