[Top][All Lists]

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

Re: Gitlab Migration

From: Daniel Brooks
Subject: Re: Gitlab Migration
Date: Thu, 02 Sep 2021 11:26:04 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Daniel Brooks <db48x@db48x.net>
>> Cc: Dmitry Gutov <dgutov@yandex.ru>,  cpitclaudel@gmail.com,
>>   emacs-devel@gnu.org
>> Date: Thu, 02 Sep 2021 08:30:55 -0700
>> Eli Zaretskii <eliz@gnu.org> writes:
>> > Way better than Github and its ilk, where I actually need to point my
>> > browser to the issue to see the comments.
>> I use the Magit and Forge packages to create, view, and reply to merge
>> requests from Github and Gitlab inside of Emacs. No web browser needed.
> How do you know there was a merge request?

For the small projects I work on, it is sufficient to open the list of
merge requests from Magit. This is no different than opening my email
inbox to see if there are new emails. Unlike a real email inbox,
however, nothing is keeping track of which “messages” I have read; I
have to do that myself. For a large project I would want some other way
to keep track of that information.

Since there is no Gnus integration yet, I assume that most people read
their email notifications to find out what has changed, then use Forge
or some other means to act on that information. Now that I think about
it, I think that forges should provid all the merge requests via IMAP,
rather than inventing yet another rest api.


reply via email to

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