todo.txt

#
# REWORK TODO LIST
#

# [x] make bug_suite output new structure
# [x] cleanup bugsuite
# [x] cleanup and rework (1)
# [x] cleanup and rework (2)
# [x] cleanup and rework (2.1)
# [x] cleanup and rework (3)
# [x] check all code again
# [x] look at concurrency locks
      Not good, mainly because comments could get lost or things inside the ifs after first creation :(
# [x] check if we can reduce needed permissions and filters.
# [x] readme
# [x] readme link workflows and relative paths
# [x] security and bug issue template
# [x] finish review of 3.js
# [x] latest compiler output
# [x] rename template to tid_PRid_CEC0.jai


#
# FOR RELEASE
#
# [ ] maybe exclude logs from change detection?
# [ ] think about bugs with modules again (probably modules folder inside bug folder?)
# [ ] add labels for new and just fixed issues
# [ ] maybe also add -x64 backend
# [ ] think about detecting sb via label instead
# [ ] for issue update in bug suite make rate limit works, for when a new version is released
# [ ] PR template
# [ ] test BB pipeline
      currently problemo, because createTree is failing on forks, even with all permissions...

# [-] making the test run without offline platform? How?
       NOTE: Not directly possible (https://github.com/orgs/community/discussions/50926)
             For when its stuck. Its possible to check completely offline though
# [x] update issue template to support is_runtime_test
# [ ] notify me when something changes but passed test was same (compiler output for example)
# [ ] change emailed in handling and add lable for it
# [ ] history (de)compression
# [ ] optional checking if test really crashes on latest version after manual approval
# [ ] create the categoreies list for issue clasification
# [ ] add machine os data etc to issue like windows version, take a look at runner envs
# [ ] fix issue links in readme