Note: Trashed issue template as it is not relevant
This is something I recommend for the long term and is by no means a priority, however I think if this project is to stay alive for a long time it would greatly benefit from an automated system to review codes with "working", "not working" or "maybe working" kind of system.
In the iOS jailbreaking community we have a project that also runs through GitHub that does something like this for Cydia Tweaks, you can find it as tweakCompatible here. It relies on a specific issue format that the tweak generates for the review and a GitHub bot to process those issues. Then it has a github io hosted front end webpage to view all the reports (as well as integrating into Cydia but that's probably not in the scope of 3DS since the cia app doesn't use webviews)
Along with this could also come a system for automatically submitting new cheats through another template, for this either the repo's issue template could be edited to include a disabled (wrap in <!-- -->) section for the cheat submission template or a form service such as google forms could be used to send the data here based on user input there.
Note: Trashed issue template as it is not relevant
This is something I recommend for the long term and is by no means a priority, however I think if this project is to stay alive for a long time it would greatly benefit from an automated system to review codes with "working", "not working" or "maybe working" kind of system.
In the iOS jailbreaking community we have a project that also runs through GitHub that does something like this for Cydia Tweaks, you can find it as tweakCompatible here. It relies on a specific issue format that the tweak generates for the review and a GitHub bot to process those issues. Then it has a github io hosted front end webpage to view all the reports (as well as integrating into Cydia but that's probably not in the scope of 3DS since the cia app doesn't use webviews)
Along with this could also come a system for automatically submitting new cheats through another template, for this either the repo's issue template could be edited to include a disabled (wrap in
<!-- -->) section for the cheat submission template or a form service such as google forms could be used to send the data here based on user input there.