Re: Need help with GitHub Issues migration
Oswald Buddenhagen via mc-devel <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> Tue, 25 Feb 2025 16:26:48 +0100
| Newsgroups | gmane.comp.gnome.apps.mc.devel |
|---|---|
| Message-ID | <Z73hOAvDpRGlq_9y@ugly> |
On Tue, Feb 25, 2025 at 03:34:44PM +0100, Yury V. Zaytsev wrote: >All right, you convinced me. Let's give it a try. I have set up ticket >templates and enabled Discussions: > >https://github.com/MidnightCommander/mc-test-1/issues/new/choose > >This is what it's going to look like. I hope this will keep the amount of junk at bay. > looks good. fwiw, in the bug template, a word is missing: "I confirm the issue is still reproducible with the [latest] version of Midnight Commander". is it possible to convert the PR template to a form as well? it's _remarkable_ how many people don't delete the instruction text ... >> [...] i still see around a dozen double submissions resulting from >> trac acting up. > >Thanks for the hint, I took care of what I could find. > one left! :-)=) https://midnight-commander.org/ticket/4024 >Before: > >https://github.com/MidnightCommander/mc-test-1/issues/3972 > >After: > >https://github.com/MidnightCommander/mc-test-1/issues/4665 > >Do you think it's better now? > yep, excellent. >> have you considered converting tickets with patch attachments into >> PRs? > i should clarify that i meant the migration. come to think of it, i should not have asked about patches, but the branch/commit links. these are already well-formed, so fundamentally shouldn't pose a problem. in fact, it would seem to be only a small step from what you already built, though i haven't thought through the implications for the comment trails. -- mc-devel mailing list mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org https://lists.midnight-commander.org/mailman/listinfo/mc-devel