GitHub Issues & Discussions

[jdx]

Due to the volume of issue submissions mise received, using GitHub Issues became unsustainable for the project. Instead, mise uses GitHub Discussions which provide a more community-centric platform for communication and require less management on the part of the maintainers.

Please note the following discussion categories, which match how issues are often used:

• Announcements
• Ideas: for feature requests, etc.
• Troubleshooting & Bug Reports

[rsyring]

And, in case you missed it, the project is also on Discord .

[idelsink]

Downside of discord, besides it being nice to talk to people, is that information gets locked and unsearchable;

Related to this change of switching to discussions, all google issue search results are now dead 😢 as clicking on issue search results now show, so now I have to search for the title provided by google in the discussion search topic, not ideal. Would have been great if all the issues would remained and just redirected, or locked. But this might be more a GitHub issue then Issue to Discussion issue

[beeburrt]

...information gets locked and unsearchable

I agree

You might be able to use Internet Archive to find old issues. like so:
https://web.archive.org/web/20250000000000*/https://github.com/jdx/mise/issues/2961

But that depends on if the particular issue you are looking for was archived.

[CherryDT]

@jdx Please reenable issues and configure it in such a way that no new issues can be created. Set a template users must select which prominently states that all issues are auto-closed and discussions should be used instead. Then add a bot which auto-closes any newly opened issue.

This way, we can still browse all existing issues. This is a big problem right now, whenever you google something about mise you find GitHub issues which have very interesting contents according to the google preview, but then you get a 404 when you click on it!

[CherryDT]

You may well survive, but all of us get frustrated. It's like a carrot on a stick: The solution is clearly there but you can't reach it!

[jdx]

There really weren't that many issues, especially since we were already doing things as you described for a year. I did migrate all of the issues referenced in the codebase and docs, there was 4 of them not including in e2e tests.

[CherryDT]

I didn't mean referenced in code or docs, I mean when I google about any issue or question I have in mise, I find several issues which sound relevant (at least to give me a better understanding or context) and get frustrated when I get the 404 upon clicking on them. After this happened to me now around 8-10 times, I decided to open a discussion about it, found this existing one and posted.

The 14 other upvotes on the above post by @idelsink prove me right, I'd say.

(In my personal opinion, destroying any information that existed on the Internet is one of the worst things one can do, that's why I always try to keep links alive forever, even after moving to new platforms and such. Unfortunately archive.org does not have issues indexed. I know it's always a little hassle to keep links working, that's why I sent you some sponsorship money, to hopefully make the effort worth your while if you do decide to actually do it - and also as token of appreciation because mise is the best solution to several problems I had over the last few years.)

[jdx]

whatever issues these are had out of date information. I agree it would be better to preserve it in amber but github doesn't allow that option. I also was not happy with having the misleading issues tab.

[CherryDT]

I see. Thanks.