Re: Need help with GitHub Issues migration
"Yury V. Zaytsev via mc-devel" <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> Mon, 24 Feb 2025 09:53:51 +0100
| Newsgroups | gmane.comp.gnome.apps.mc.devel |
|---|---|
| Message-ID | <[email protected]> |
> On 23. Feb 2025, at 22:58, Max <mleonov-g/[email protected]> wrote: > > 2. Choose a GitHub UI for project management: > https://github.com/Project-managment-templates That's really cool to see, thanks! Unfortunately not applicable for us, but good to know that GitHub now seems to have reasonable project management options. Very impressive and looks usable with little effort. > 3. Think through the project's use of GitHub labels for both the issues and pull requests: > https://github.com/abdonrd/github-labels > https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues > https://seantrane.com/posts/logical-colorful-github-labels-18230/ > https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63 > https://climbtheladder.com/10-github-labels-best-practices/ I'm managing the labels with Pulumi and I'm pretty happy about it. Also, I've already developed a structure that was presented in the first post. I'm rather looking for concrete suggestions on how to improve it. If there are none, that's fine too. It means our system is perfect :) -- mc-devel mailing list mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org https://lists.midnight-commander.org/mailman/listinfo/mc-devel