Closed Offirmo closed 3 years ago
Hi @Offirmo.
I just made a tiny script to figure out how many repositories are using dev-to-git
and how many blog posts are being published with it.
It turns out that dev-to-git
currently powers 224 blog posts across 88 different repositories :)!
Anyway. Nothing has changed recently on this codebase so unless there's been a breaking change on dev.to's API I don't see how this could "break" dev.to. Your title seems a bit excessive, doesn't it? At least you're the first one reporting this so we'll see if anyone else encounters this in the next few days
I strongly advise NOT using dev-to-git while the linked bug is not fixed.
dev-to-git
is a free tool developped on my own time and I don't get paid to maintain it.
Don't get me wrong, I'd be happy to do so but with a proper issue showing some investigation and explaining how to repro.
Also, you do not have to use dev-to-git
to publish on dev.to. This is just a CLI. Feel free not to use it and write your blog posts directly from dev.to UI
Hi @maxime1992
I didn't intend to criticize your awesome tool, I should have stated that I also had suspicions that the problem could come from anywhere, for example the dev.to APIs themselves may be not robust. I edited the initial bug report above to make it clearer.
Once again, I apologize for not having been clear enough when reporting. As my whole dev.to was broken, my intention was only to warn other users.
Anyway, the problem has been fixed, it was coming from dev.to (see linked tickets in https://github.com/forem/forem/issues/11690)
again, the problem has been fixed, it was coming from dev.to (see linked tickets in forem/forem#11690)
EDIT: 2020/12/08 bug fixed, came from dev.to
After following the blog post instructions, I managed to use dev-to-git to upload a test blog post.
I extended to a second blog post, then dev.to broke. I can no longer blog on dev.to nor edit an existing blog post, always getting 404.
I reported the issue to dev.to https://github.com/forem/forem/issues/11690
At this point, one can't tell if the bug is from
dev-to-git
, fromdev.to
or from the interaction of them = I'm not blaming dev-to-git.But just in case I suggest NOT using dev-to-git while the linked bug is not fixed, especially if your dev.to blogposts are critical to your business.