[DOCS] Update repository links to the fivetran org - #12126
Open
iamfeldman wants to merge 4 commits into
Open
Conversation
👷 Deploy request for niobium-lead-7998 pending review.Visit the deploys page to approve it
|
Author
|
@cla-bot check |
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.
What this fixes
Four docs still point contributors at the old
great-expectations/great_expectationsorg after the move tofivetran/great_expectations:DEVELOPMENT.md— tells new contributors to set theirupstreamremote to the old org's SSH URL, so a fresh dev setup tracks the wrong repositorydocs/README.md— the docs-contribution guide's "browse the topic file" link goes to the old org's treedocs/docusaurus/docs/help/get_support.md— the "Issues and PRs" support linkdocs/docusaurus/docs/help/compatibility_reference.md— the core/optional dependency links (requirements.txt,reqs/)GitHub's rename redirect makes these work today, but the contributor-path ones actively teach the wrong remote, and redirects stop being guaranteed if the old name is ever reused.
Five URL substitutions, no content changes — completing the same rename already applied elsewhere in
DEVELOPMENT.md. Found while reading the contributor docs as a first-time contributor.