From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: a package to connect to github issues
Date: Sat, 31 Aug 2024 18:23:53 +0300 [thread overview]
Message-ID: <35926.9514957973$1725117869@news.gmane.org> (raw)
In-Reply-To: <86h6b8lrw7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 25 Aug 2024 15:16:08 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Matthias Meulien <orontee@gmail.com>
>> Date: Sun, 25 Aug 2024 08:49:13 +0200
>>
>> > To pull and push to GitHub, you can use Git as usual, since GitHub is
>> > a Git repository.
>> >
>> > But you said "connect to issues on GitHub", so how does on "connect"
>> > or "pull and push" with issues?
>> >
>>
>> I guess the OP want to fetch issue descriptions, render and edit the issue
>> descriptions, browse comments, write replies, change issues status, etc.
>> all in Emacs. Not in his web browser.
>
> If the access being sought is via email, then GitHub lets users ask
> for all the discussions to be sent via email. Issues are sent to
> those who submitted them or subscribed to them.
That's true however email replies are moved into the right context when
replying to inline commits on code changes.
Github (and also other forges such as Gitlab) allow for comments threads
on specific line of code.
It still works but they could map the emails better.
next prev parent reply other threads:[~2024-08-31 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 16:10 a package to connect to github issues Uwe Brauer via Users list for the GNU Emacs text editor
2024-08-24 16:16 ` Eli Zaretskii
2024-08-24 16:49 ` Uwe Brauer via Users list for the GNU Emacs text editor
2024-08-24 18:54 ` Eli Zaretskii
2024-08-25 6:49 ` Matthias Meulien
2024-08-25 12:16 ` Eli Zaretskii
2024-08-25 12:58 ` Uwe Brauer via Users list for the GNU Emacs text editor
2024-08-25 13:24 ` Juergen Fenn
2024-08-25 18:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-08-31 15:45 ` Björn Bidar
2024-08-31 15:23 ` Björn Bidar [this message]
2024-08-24 17:56 ` Rudolf Schlatte
2024-08-25 12:59 ` Uwe Brauer via Users list for the GNU Emacs text editor
2024-08-25 13:29 ` Suhail Singh
2024-08-25 16:06 ` Uwe Brauer
2024-08-27 19:41 ` [Success] (was: a package to connect to github issues) Uwe Brauer via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='35926.9514957973$1725117869@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).