loading...

re: Manage your dev.to blog posts from a GIT repo and use continuous deployment to auto publish/update them VIEW POST

TOP OF THREAD FULL DISCUSSION
re: this way seems like an extra step that you need to make before the post. You always need to get the draft id before it posts.
 

It doesn't seem like it is. It clearly is 🙄. Unfortunately it's the best I could come up with as dev.to do not use UUIDs. Otherwise it'd have been easy to generate one 🤷‍♂️ here the only way to automate that part would be to correlate the blog post title but it'd be an issue if you update it (which is obviously not great). As it's a one time thing for an article, I think it's not too bad either though

 

Maxime, first of all, thanks for the cool idea 👍
I have a couple of questions/suggestions:

  1. (on Jay's concern) Why not try to use dev.to API's POST request and get an article ID with the response?
  2. Didn't you try to replace Travis with Github Actions? This way one gets the opportunity to use the workflow with a private repo

Hi Fyodor, thanks :)!

1) It'd be great for sure to have something in command line and we've got an issue here github.com/maxime1992/dev-to-git/i... if you have further ideas on that please share there

2) I did not as I'm not yet familiar with github actions. I'd be happy to have a PR if you feel like it though! :) Could you please open an issue first there github.com/maxime1992/dev-to-git/i... so we can discuss it and then we can talk about a PR

Thanks

Thanks for the coordination Maxime! Zak's ideas on id handling look comprehensive, they just need to be implemented) As for github actions, I'm not very familiar with that too, need to research, and I would be happy to contribute if I have enough time, you know. Added the issue to discuss further 👌

code of conduct - report abuse