Repository navigation
docs: strengthen the Altifigence public developer profile - #2
Merged
Merged
Conversation
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.
The organization profile had no developer entry points or shared community guidance. Add a focused project map, SDK and official Docs links, and explicit publication, license and host-availability boundaries.
Add repository-default contribution, support, private security reporting, conduct, issue and PR guidance. Apache-2.0 covers this repository's materials only. Add a read-only CI check for tracked public files and local Markdown links.
Validation:
node scripts/check.mjsandgit diff --cached --checkpass. Reviewed the four public tool repositories and their actual release scope; this change does not publish product source or claim DDS product availability.