We need to clean up root repository folder
package.json and package lock json should go to web, were they are needed, not in root as this is multilanguage repository, not javascript only repository.
Also .gitkeep should be removed.
https://github.com/link-foundation/link-cli/blob/main/README-WASM.md
https://github.com/link-foundation/link-cli/blob/main/WEBASSEMBLY_IMPLEMENTATION.md
Should be moved to README.md of web (if this is where wasm implementation resides, even better to have ./js folder, in case we will later have JavaScript implementation. So web should be moved to ./js folder with package files.
And these md files should be merged in README.md of ./js folder, so everything will be there, if file too large you can split it but inside this folder.
https://github.com/link-foundation/link-cli/tree/main/ci-logs folder should be moved to some place in ./docs/case-studies
as well as docs/screenshots/issue-12 also should go to ./docs/case-studies
Also I still don't see deploy to GitHub Pages in our CI/CD and no deploy to NuGet in GitHub Releases. That must be fixed.
I now switched to deploy of GitHub Pages via GitHub Actions, may be that was the part of the problem, anyway we should update folder structure, and double check everything, so everything will work as expected.
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 download all logs and 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), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, 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).
If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code.
Please plan and execute everything in a 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.
We need to clean up root repository folder
package.json and package lock json should go to web, were they are needed, not in root as this is multilanguage repository, not javascript only repository.
Also .gitkeep should be removed.
https://github.com/link-foundation/link-cli/blob/main/README-WASM.md
https://github.com/link-foundation/link-cli/blob/main/WEBASSEMBLY_IMPLEMENTATION.md
Should be moved to README.md of web (if this is where wasm implementation resides, even better to have ./js folder, in case we will later have JavaScript implementation. So web should be moved to ./js folder with package files.
And these md files should be merged in README.md of ./js folder, so everything will be there, if file too large you can split it but inside this folder.
https://github.com/link-foundation/link-cli/tree/main/ci-logs folder should be moved to some place in ./docs/case-studies
as well as docs/screenshots/issue-12 also should go to ./docs/case-studies
Also I still don't see deploy to GitHub Pages in our CI/CD and no deploy to NuGet in GitHub Releases. That must be fixed.
I now switched to deploy of GitHub Pages via GitHub Actions, may be that was the part of the problem, anyway we should update folder structure, and double check everything, so everything will work as expected.
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 download all logs and 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), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, 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).If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code.
Please plan and execute everything in a 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.