From: Uwe Brauer <oub@mat.ucm.es>
To: help-gnu-emacs@gnu.org
Subject: Re: how to connect emacs (gnus) to github pull-requests discussions
Date: Sat, 19 Dec 2020 18:01:06 +0100 [thread overview]
Message-ID: <875z4xivcd.fsf@mat.ucm.es> (raw)
In-Reply-To: CAP_d_8WcL7=HRtv955Vcz9r3SvgSF6bB70yEazn6g6=ag_1LiQ@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
>>> "YK" == Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Sat, 19 Dec 2020 at 23:04, Uwe Brauer <oub@mat.ucm.es> wrote:
>> More and more code development is done by pull requests (mostly using
>> github) One of most annoying thing for me is that I cannot use emacs
>> more specifically gnus to access these discussions.
>>
>> Does somebody know either a possibility to connect gnus to github pull
>> requests or any other emacs pkg that would allow me to connect emacs to
>> the github pull request pages
> Why not?
> Github lets you subscribe to any individual issue, pull request, or a
> whole repository.
> If you are subscribed, Github will send you an email every time
> someone posts a comment in that issue or pull request, or if someone
> creates a new issue or PR in that repository.
> Every such notification email has its Reply-To header set to a unique
> email address. Any reply you send to that address will be added as a
> comment to the corresponding issue or PR. (It will be interpreted as
> Markdown so quoting works as expected. Just don’t overquote.)
I see, I used gnus-summary-followup-with-original (old habit) and that
was a mistake, also I think it is better not to (smime/pgp) sign your message
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-12-19 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 16:04 how to connect emacs (gnus) to github pull-requests discussions Uwe Brauer
2020-12-19 16:28 ` Yuri Khan
2020-12-19 16:36 ` Uwe Brauer
2020-12-19 17:00 ` Yuri Khan
2020-12-19 17:01 ` Uwe Brauer [this message]
2020-12-19 18:21 ` Stefan Monnier
2020-12-19 21:15 ` Uwe Brauer
2020-12-19 21:28 ` Sébastien G
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=875z4xivcd.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).