update loot-console-logger

[emerycp]

• added a new sidebar that lets you log like a feed, apply filters, and track via a summary.
• updated the base code for logging in the console.
• added more options in the settings for greater customization.
• rewrote a more comprehensive README.

[runelite-github-app]

Plugin repository has changed

loot-console-logger: d09ce0e13c84bd5679e5bedd52ec368976bf2c0f..d0ce0f5ff91110b2cbe8ec0ceb9d439c0ba5802e

[runelite-github-app]

This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed.

---

Internal use only: Reviewer details Maintainer details

[Felanbird]

You're submitting the entire plugin-hub in this PR, please don't do that.

[emerycp]

You're submitting the entire plugin-hub in this PR, please don't do that.

Yep, mistake on my end, sorry!
I mistakenly rebased on plugin-hub. I created a new repo, and I updated the commit hash to the latest commit on the new repo. It should be good now.

[riktenx]

the commit hashes should match

[riktenx]

you should be forking the original thing or mirror-pushing the branch to another repo if you know how to do that basically

[emerycp]

you should be forking the original thing or mirror-pushing the branch to another repo if you know how to do that basically

I renamed the old repo to loot-console-logger-old and created a new one with the original name, loot-console-logger, and a freshly forked copy of example-plugin, then mirrored all my changes to fix my mistake of rebasing on plugin-hub.

I think the RuneLite GitHub bot didn't count it as a change and that's why the hashes don't match. The commit hash is set to the latest commit of the newest repo but the bot's comment has an old hash pointing to the old repo. Should I open another PR, and close this one ?

[Alexsuperfly]

rewriting the history like you did means we have to review this as an entirely new plugin again, you will need to restore the original history if you want this to be reviewed as a plugin update.