[draft] 11228 universal file transfer #50846
Draft
Conversation
This file contains 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
…space between lines in the same list object.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
octavia-squidington-iii
added
the
area/documentation
ian-at-airbyte
commented
Dec 31, 2024
| @@ -279,4 +279,8 @@ table tr:hover { | |||
| } | |||
| table thead tr:hover { | |||
| background-color: transparent; | |||
| } | |||
|
|
|||
| .markdown li > p { | |||
There was a problem hiding this comment.
This is not related to anything, but it fixes an oddity where list items in the final docs had variable top and bottom margins depending on how an author spaced things out in their MarkDown.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Proposed user docs for universal file transfer / copy raw files. Includes some unrelated fixes to the S3 source docs, which Airbyte wasn't parsing properly in-app. Before I switch to a regular PR I'm mostly curious if you feel like the scope is right or if there are things on which we should go into more depth.
How
Added a new "delivery methods" topic. Updated existing connector topics with a new step that references the new concept.
Review guide
User Impact
Users will be able to read about copying raw files and hopefully realize it's even an option.
Can this PR be safely reverted and rolled back?