all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: help-gnu-emacs@gnu.org
Subject: Re: a package to connect to github issues
Date: Sat, 31 Aug 2024 18:45:54 +0300	[thread overview]
Message-ID: <48196.4183434442$1725119205@news.gmane.org> (raw)
In-Reply-To: <87a5h0u5cs.fsf@mat.ucm.es> (Uwe Brauer via Users list for the's message of "Sun, 25 Aug 2024 14:58:11 +0200")

Uwe Brauer via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

>>>> "EZ" == 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 is correct.
> However, the problem is that github encourages the use of markdown
> syntax for example to emphasize source-code (well and other structures I
> do not care about much).
>

IMHO it really depends on your workflow. You try to reply Email with a
Github/Forge app/mode it might not be so easy to adjust to. Since
these apps don't notify you on issues in the same way and display new messages
in a way you can with email unless they specifically focus on a good
user experience when working on bugs.
You can markdown support but loose the other features you have unless
the apps are in a good shape to be useful.

Further not all forges offer the same integration via the API that any
app would use compared to what their website offers.
I.e. Github doesn't allow to select which email is used when merging
pull requests using their API but on the website its possible.

> The point is that if I add markdown syntax in my email replies, the
> github software deletes that syntax, the reason is not clear to me,
> maybe to fight spam.  

I don't change the mime-type of my emails however Github still does
recognize the markup of email e.g. when quoting another person.

The ruby package they use to parse email replies you can find here:
https://rubydoc.info/gems/email_reply_parser/

IMHO the added markdown support isn't worth the effort. For email
replies to work better is something only they can fix.



  parent reply	other threads:[~2024-08-31 15:45 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 [this message]
2024-08-31 15:23           ` Björn Bidar
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='48196.4183434442$1725119205@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.