This repository was archived by the owner on Nov 17, 2024. It is now read-only.
Labels
Labels
30 labels
- An issue that never goes stale
- Good for newcomers
- Extra attention is needed
- This applies to browser-based or online games only
- This issue is about continuous integration and deployment of ct.js via automation
- Pull requests that update a dependency file
- This requires changes in the exporter that bakes ct.js games
- This involves changes to ct.IDE, its UI and logic
- This affects core ct.js library
- This issue describes a functionality that is implemented (or should be) in a module
- This issue or pull request already exists
- This doesn't seem right
- This aged well. Probably not relevant now.
- This will not be worked on
- Some work was done before to fix this issue
- Something isn't working
- Meaning a part of a technical debt: something prone to errors, or complicating the development
- An improvement to an existing functionality
- A complex issue that decomposes into a big number of tasks, affecting various compo 3BB6 nents of ct.js
- Something truly new that expand the functionality of ct.js
- This issue comes from one of the dependencies
- This issue is about working with ct.js more efficiently as a user