fix: icons are no longer displayed after css-loader major upgrade

[ahochsteger]

This reverts commit 7063434.

Fixes #1728

[coveralls]

Pull Request Test Coverage Report for Build 1270762142

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 29.602%

---

Totals
Change from base Build 1268797050:	0.0%
Covered Lines:	3671
Relevant Lines:	13045

---

💛 - Coveralls

[firstof9]

You also need to fix your commit message.

[ahochsteger]

You also need to fix your commit message.

@firstof9, I've seen the complaint about "Semantic PR title / commit message" and then already changed the title of the PR to comply to conventional commits.
Shouldn't this be enough?

[firstof9]

Nope your commit message also needs to follow suit.

[ahochsteger]

Nope your commit message also needs to follow suit.

@firstof9, done.

[firstof9]

Cheers!

[blhoward2]

@ahochsteger you can also try @zwave-js-bot rename commit next time. It only matters for single commit PRs. I think anyone can run that in their PR but may be wrong.

[robertsLando]

Ok, will try to fix the breaking changes once I come back. Thanks!

[ahochsteger]

@blhoward2, thanks, I was not aware, that for single-commit PRs the real commit message must be changed. I thought the PR title can be used as well for the merge commit.
I've done so with git commit --amend and git push --force (see this event) but I am unsure if this is really the way it should be done?
Usually I prevent force-pushing to Github ...

[blhoward2]

I'm not sure there is a right way. I've seen people force push. I've seen others push empty commits. I'm honestly not the expert because rarely do I do anything in one commit. 😬 We frequently use the bot to fix it for submitters.