docs: add Anycloud to deployment compute - #4
Open
0717lee wants to merge 2 commits into
Open
Conversation
Add the Anycloud Deployment/compute entry to data/projects.json and update README coverage from 500 to 501 so the catalog and table stay aligned.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #3.
Add Anycloud to the Deployment/compute section next to the closest portable multi-cloud entry, and keep
data/projects.jsonaligned with the README table.The wording is limited to capabilities supported by first-party evidence:
Changes
README.md: one Deployment/compute row for Anycloud; coverage count500→501data/projects.json: matching Anycloud entry (category: Deployment/compute)Verification
anycloud-sh/anycloud-skills, including Codex/Agent Skills supporthttps://anycloud.sh/, getting started, and the skills repository return HTTP 200best_formatch the JSON entrygit diff --checkCoverage is 501 because this branch is based on current
main(500 entries). If #5 merges first, this PR should be rebased onto latestmain, the count updated to 502, and the JSON tail conflict resolved.