This message was deleted.
# secoda-supportw
wooden-spring-14915
03/31/2022, 1:16 PMThis message was deleted.
đź‘€ 1
e
elegant-house-93198
03/31/2022, 1:24 PM
Hey Richard, just so I’m understanding correctly, do you mean that you’d want to push all the markdown content of the the documents associated to a collection in GitHub? If that’s correct, it would be good to understand what structure you’d like the data to have?
g
gifted-translator-12305
03/31/2022, 1:50 PMyea im not sure what is possible as far as structure goes... I have a collection on github of individual markdown files with images and content populated and I would like the ability to "publish" these markdown files to secoda without having to manually copy over would be the dream.
gifted-translator-12305
03/31/2022, 2:17 PMlooking deeper i see there is a way to link a github repo to secoda for "backup" currently enabling that now to see how I can use it. Being able to edit the markdown on my local machine and then update the repo and it finds its way into secoda may be to much to ask for from this but going to look into what I can do with this connection.
gifted-translator-12305
03/31/2022, 2:37 PMyea may not be what im looking for as it ouputs a bunch of json meta data....
e
elegant-house-93198
03/31/2022, 2:41 PM
I was going to mention the git integration @gifted-translator-12305. It is a bunch of json meta data but included in that metadata is the markdown documentation content. It’s currently only one way from Secoda -> git, but I imagine even if it was Secoda -> git and git -> Secoda it wouldn’t solve your use case here.
One thing you could immediately do is use the API, but that doesn’t solve the version control issue. Let me add this item to our backlog and I’ll let you know if the rest of the team has any ideas about the best way we can solve it.
g
gifted-translator-12305
03/31/2022, 3:05 PMyea the API was our first thought too. Thank you for keeping me posted.
2 Views