Style Transfer Template

[The-ML-Hero]

Summary

I just added the style transfer template

Checklist

• [ ] all tests are passing (see README.md on how to run tests)
• [ ] if you created a new template: it contains a file test-inputs.yml, which specifies a few input values to test the code template (the test is then automatically run by pytest)
• [ ] you formatted all code with black
• [ ] you checked all new functionality live, i.e. in the running web app
• [ ] any generated code is formatted nicely, both in .py and in .ipynb ("nicely" = comparable to the existing templates)
• [ ] you added comments in your code that explain what it does
• [ ] the PR explains in detail what's new

[EbilPanda]

sry the PR gets polluted by other commits I'm currently testing...don't know how to disable this

[hsuanxyz]

@EbilPanda Hi, Thank you for your PR! But now can not release the new version, please revoke your changes for README.md&package.json, then I will merge.

[bragayann]

Hey @EbilPanda, really nice contribution!

What you can do is:

• Check until which commit you want to have to this PR.
• Get its hash
• Do git reset --hard yourhash. example: git reset --hard b3d637b for the updated readme... one
• Force push the repo like git push origin -u yourbranch -f

I'd recommend you to create a new branch based on your current one(just for backup), though.

[EbilPanda]

I have gone back on my baster branch and also made a branch out of it :) will make the other feature I'm currently on directly as a branch :)

hope everything is okay now -> have removed readme commit and revert the change to package.json