add td_result_export.md to index#1768
Merged
yoyama merged 1 commit intotreasure-data:masterfrom Sep 26, 2022
Merged
Conversation
yoyama
approved these changes
Sep 26, 2022
Contributor
yoyama
left a comment
There was a problem hiding this comment.
LGTM. Thank you for your contribution.
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
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.
Purpose
To make td_result_export more visible by adding it to the index of the Treasure Data operator.
https://docs.digdag.io/operators/treasure_data.html
This is the current page index. td_result_export is not listed here, so it is hard to find the operator if they don't know the operator.