Time  Nick       Message
10:08 [MatrxMT]  <Zughy> I suggest that we avoid using the new Github "type" function when we label issues, as we've already got a label system and starting now would result in a situation where old issues don't have a type and new ones do
10:08 [MatrxMT]  <Zughy> Nor I want to manually label 1200+ issues
14:54 rubenwardy merging #15254 in 10
14:54 ShadowBot  https://github.com/luanti-org/luanti/issues/15254 -- ContentDB: Add reviews tab by rubenwardy
15:07 rubenwardy Zughy: might be possible to set the type in bulk, you can do this with labels
15:13 [MatrxMT]  <Zughy> hopefully
15:58 sfan5      it is possible
17:07 [MatrxMT]  <Zughy> Good: next question is, if we ever migrate, will we lose Bug and Feature labels as they're not labels anymore?
17:15 rubenwardy That depends whether the importer has been updated to understand types
18:23 [MatrxMT]  <y5nw> It would also require the forge software to support issue types (separately from issue labels); this does not seem to be the case for Forgejo/Codeberg at the moment
22:12 [MatrxMT]  <grorp> great to finally have the CDB reviews PR merged :)
22:14 [MatrxMT]  <grorp> y5nw: not if the import process supports converting them back to labels
22:14 [MatrxMT]  <grorp> anyway, I don't see a need to do the work to migrate to github's new issue type feature, labels work 🤷