search

ipfs-shipyard / ipfs-deploy

Zero-Config CLI to Deploy Static Websites to IPFS
Other
1.16k stars 122 forks source link

chore: move to shipyard #80

Closed hacdias closed 5 years ago

hacdias commented 5 years ago

Ignore failing CI (due to linting reasons). Will be solved in #79.

@agentofuser I removed most of the deploying process. The scripts wouldn't work on Windows due to their sh nature.

About the commits: we have a good policy of using conventional commits all the time. I removed the checks since all should go through PRs and the final hit to squash is when the commit message is finally written.

Also, removed the All Contributors (burden to maintain) and added a link to GitHub contributors page. Gave you a paragraph of thanks for starting this project 😃

agentofuser commented 5 years ago

@hacdias great stuff! Thank you for picking up the baton! =)

I'm going to see if there is a way to redirect my scoped npm package to the global one. Happy graduation cerimony, ipfs-deploy :D 🎓🎉

Also thanks to @olizilla and @kanej for your contributions 🙏

Always Be Defrictioning 🥌 😃

Macil commented 5 years ago

I'm going to see if there is a way to redirect my scoped npm package to the global one.

You can mark an npm package as deprecated and include a deprecation message saying "Package x is the continuation of this package". The package will continue to work but npm will print that message out when the package is installed.

agentofuser commented 5 years ago

@Macil Perfect, thank you! Just did that: https://www.npmjs.com/package/@agentofuser/ipfs-deploy