unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Ruijie Yu via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: help-gnu-emacs@gnu.org
Subject: Re: elisp pkg for dealing with github/gitlab issues
Date: Tue, 25 Apr 2023 22:23:01 +0800	[thread overview]
Message-ID: <sdvbkjcrq77.fsf@netyu.xyz> (raw)
In-Reply-To: <87a5ywuvl6.fsf@mat.ucm.es>


Uwe Brauer <oub@mat.ucm.es> writes:

> Hi
>
> I know that github/gitlab issues can be dealt, partially via email.
>
> Does anybody know about recent elisp packages supporting the direct
> connection with the issue system?
>
> The package manager list some of them, but they are all quite old, and I
> could not make them work.
>
> Anybody has an suggestion?
>
> Regards
>
> Uwe Brauer 

I used to use magit[1] + forge[2] to work with GitHub via Emacs, but for
some reason it no longer compiles for me, (and that my internet speed
for GitHub is no longer fast enough for me to use it anyways,) so I
stopped bothering to try to fix it nor use it.  It might just be myself,
so you can take a look and see if it works for you.

Note that while magit is on nongnu elpa, forge is on neither gnu or
nongnu elpa, so you either have to resort to Melpa (or elsewhere), or
build from source, which apparently failed for me.

Also, while trying to get forge to compile, I noticed that it has a
bunch of dependencies targeting all major VC sites like github, gitlab,
bitbucket, etc.  So, if it compiles, it should probably cover your
needs.

[1]: https://github.com/magit/magit
[2]: https://github.com/magit/forge

-- 
Best,


RY

[Please note that this mail might go to spam due to some
misconfiguration in my mail server -- still investigating.]



      reply	other threads:[~2023-04-25 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 10:04 elisp pkg for dealing with github/gitlab issues Uwe Brauer
2023-04-25 14:23 ` Ruijie Yu via Users list for the GNU Emacs text editor [this message]

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=sdvbkjcrq77.fsf@netyu.xyz \
    --to=help-gnu-emacs@gnu.org \
    --cc=oub@mat.ucm.es \
    --cc=ruijie@netyu.xyz \
    /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).