All JavaScript related files should go to ./js folder, and be controlled by js.yml. And rust goes to ./rust folder and controlled by rust.yml. Project files and other related files should be separated, and root of repository should contain only common files for both languages. Each language should have its own ./js/scripts and ./rust/scripts folder, with CI/CD scripts in js and rust as in templates.
We should clearly mark separate releases for JavaScript and Rust. They should have their own separate README.md files for examples and what actually will go to package managers and so on.
GitHub releases should be separate and should contain corresponding badges.
The root README.md should contain common information that is valid for both languages, and links to specific language versions.
Use all the best practices from CI/CD templates (check full file tree to compare for all GitHub workflow and CI/CD scripts file), if the same issue is found in template report issue also in templates:
We should compare all files, so we don't have more CI/CD errors in the future and reuse all the best practices from these templates.
We need to collect data related about the issue to this repository, make sure we compile that data to ./docs/case-studies/issue-{id} folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), list of each and all requirements from the issue, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).
Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.
All JavaScript related files should go to ./js folder, and be controlled by js.yml. And rust goes to ./rust folder and controlled by rust.yml. Project files and other related files should be separated, and root of repository should contain only common files for both languages. Each language should have its own ./js/scripts and ./rust/scripts folder, with CI/CD scripts in js and rust as in templates.
We should clearly mark separate releases for JavaScript and Rust. They should have their own separate README.md files for examples and what actually will go to package managers and so on.
GitHub releases should be separate and should contain corresponding badges.
The root README.md should contain common information that is valid for both languages, and links to specific language versions.
Use all the best practices from CI/CD templates (check full file tree to compare for all GitHub workflow and CI/CD scripts file), if the same issue is found in template report issue also in templates:
We should compare all files, so we don't have more CI/CD errors in the future and reuse all the best practices from these templates.
We need to collect data related about the issue to this repository, make sure we compile that data to
./docs/case-studies/issue-{id}folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), list of each and all requirements from the issue, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.