Feature/logo

[sirinoks]

Proposed changes

Added logo to the repo. Also made prettier ignore .svg files

Solves #30

Types of changes

• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [ ] Lint and unit tests pass locally with my changes - It might just fail on my branch, but be ok if I merge..?
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

I might struggle with the process of the PR, so I will appreciate help. Also, feel free to tell me where to better put this.

[CLAassistant]

All committers have signed the CLA.

[codecov[bot]]

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/website@886fb47). Click here to learn what that means. The diff coverage is n/a.

:exclamation: Current head 3ed6530 differs from pull request most recent head d20dfe2. Consider uploading reports for the commit d20dfe2 to get more accurate results

@@                Coverage Diff                 @@
##             feature/website      #65   +/-   ##
==================================================
  Coverage                   ?   82.42%           
==================================================
  Files                      ?       29           
  Lines                      ?      438           
  Branches                   ?        0           
==================================================
  Hits                       ?      361           
  Misses                     ?       77           
  Partials                   ?        0           

[IS2511]

@TroyKomodo PR closed without stating reason. The changes made it to the repo? How? Why is the PR closed then?

---

Solves #30

@sirinoks "solves" is not a reserved keyword on GH, but "closes" is. (Not sure if there are others, probably are.) Using that keyword makes it so a successful merge automatically closes the issue.

[IS2511]

This PR was closed accidentally, continued in

• 69 (nice)