this post was submitted on 10 Nov 2023
2 points (100.0% liked)

Emacs

310 readers
2 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis
raphael
2
Forge: no longer showing merge request numbers in Magit-log (since quite some time...) (alien.top)
submitted 1 year ago by ph0t0nix@alien.top to c/emacs
7 comments fedilink hide all child comments
 

I have been using Magit and Forge for several years, mainly with projects on self-hosted Gitlab instances. The experience has been great!

One of the nice things that Forge did for me was showing the numbers of merge requests (in !123 form) in my magit-log views. Some time ago, however, this stopped working. Actually, this stopped working quite some time ago, maybe a year or more. I was too lazy to report it and too busy to investigate. IIRC it didn't stop working right away for all repos, so I guess it is not related to e.g. upgrading to Emacs 28 (and it was definitely before I upgraded to Emacs 29.1).

To investigate this in more detail, I created new clones of several projects, but that didn't change anything. I also tried a simplified Emacs config in a new home directory to make sure that Forge's database was created from scratch. Same problem persists.

On Forge's Github pages, I found some references to interactions of Forge with bug-reference-mode, so maybe it somehow has to do with that? On the other hand, given that I used a fresh Emacs config + new clones, I guess this isn't the cause of the issue either.

Does anyone know how to get the MR numbers back in Magit's log view?

you are viewing a single comment's thread
view the rest of the comments
[–] troll-gpt@alien.top 1 points 1 year ago (1 children)

Few things to try: is the sql file still there? Did you try forge fetch all issues, maybe you need to re add it to forge, maybe forge is not loaded after opening magit, maybe forge is pointing to another remote which doesn't have issues.

[–] ph0t0nix@alien.top 1 points 1 year ago

Thanks for your reply. Let me clarify one thing: Forge works fine, in general. I can list/fetch/edit issues and merge requests. So I doubt there is a problem with the SQL file. Even more so because I ran my tests in a separate (clean) home directory.

My issue here is that in the (distant) past, whenever I opened the Magit log view with branches (Magit → l → b), I would see the merge request number (e.g. !123) for each merge commit. And now that is no longer that case.

I have tested this with two different self-hosted Gitlab instances.