Repository navigation
docs: replace deployment-specific identifiers with placeholders - #679
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.
Summary
Documentation-only change. Replace deployment-specific identifiers in docs with generic placeholders.
Why
Public docs should not name a specific deployment's buckets, cloud project IDs, console host, local home paths, or broker account numbers. Readers should substitute their own values.
Changes
<shared-bucket>orgs://<shared-bucket>/....<ibkr-project-id>.<console-url>.$QSL_WORKSPACEor are removed.U00000000.Code, workflows, and runtime-read config files are not touched.
Testing
Docs only. Local
git grepconfirms no remaining matches in Markdown files. CI runs the existing suite.Risk and rollback
None at runtime. Revert the commit to restore the previous text.
Breaking changes
none