Deprecate in repo readme #3
Etiķetes
Nav etiķešu
Nav atskaites punktu
Nav atbildīgo
2 dalībnieki
Paziņojumi
Izpildes termiņš
Izpildes termiņš nav uzstādīts.
Atkarības
Nav atkarību.
Atsaucas uz: coolaj86/acme-dns-01-cloudflare.js#3
Notiek ielāde…
Atsaukties uz šo jaunā problēmā
No description provided.
Dzēst atzaru "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
According to NPM, this repo is now deprecated, and https://github.com/nodecraft/acme-dns-01-cloudflare should be used instead.
Maybe lock down this repo for further issues/PRs, and add in the readme a link to the other repo, to avoid confusion? Like, I already did a PR to this before I realized I'm making a PR against the wrong repo, so now my time was in vain.
Deprecate in repouz Deprecate in repo readmeActually, I do want a pure JavaScript implementation of this (not ECMAScript / TypeScript), so it's not deprecated, but NodeCraft was the first to publish (coincidental simultaneous work) and uses CloudFlare regularly.
However, I do plan to eventually release pure JS implementations for each of the modules, so your contribution may not have been in vain.
My inbox is flooded with messages, and we just had our baby a few months ago, and I just switched jobs a few weeks ago, so unfortunately I didn't see your PR come in, otherwise I probably have reviewed, thanked you, and pulled it in.