Re: Need help with GitHub Issues migration

> On 24. Feb 2025, at 22:21, Max <mleonov-g/[email protected]> wrote:
> 
> - Visibility to developers as potential contributors (community = people). It takes less time for a GitHub user to contribute on GitHub. IOW, GitHub has more potential contributors who have less dedication and less availability.

I'm more worried about an influx of GitHub contributors with small, untested patches to scratch their own itch, but breaking everything for almost everyone else, and of course without any tests and/or documentation. Then you ask for changes and tests, and the usual drama about evil bureaucratic maintainers ensues. At least this is the kind of pull request we have been getting. But maybe I'm being too negative.

> If you mirror both the source code repo and docs repo on another Git host, it's hard to imagine ways in which GitHub could endanger the continuity of your package.
> FYI, it's also possible to export all GitHub issues, e.g., https://github.com/git-bug/git-bug?tab=readme-ov-file#bridges and take them with you too if need be.


This is a very nice project, but unfortunately unmaintained. The current release is broken. I haven't tried to build it from source, but the last update was in mid-2024, so I don't have high hopes for it to support newer features like issue types. I'm afraid scripting the GitHub Migrations API for backups will be the way to go :(

-- 
mc-devel mailing list
mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org
https://lists.midnight-commander.org/mailman/listinfo/mc-devel