Repository navigation
docs: clarify API key setup and track README referrals - #804
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.
Users need a concrete route from registration to a usable Ace Data Cloud API key. This updates the README setup instructions and tags first-party setup, pricing and guide links with the existing UTM convention.
utm_medium=referral,utm_campaign=evergreen, and a stable plugin-specificutm_content. Shared GitHub/package README content uses the existingopensourcesource group rather than guessing which site hosted a click.Validation:
git diff --checkpassed. The Index audit'splans/plugin-readme-audit/validate_readmes.py --repo . --base d8fb049738a701b55a322fd9cbf053946e3ecde6passed: complete/nonduplicated tags, valid values and preserved fenced examples (except verified canonical Hermes repository URL corrections).This PR prepares source documentation. Marketplace/package publication and approved-listing readback follow the existing release process after review; no version bump or deployment is claimed here. No additional adversarial review was requested.