fregante

> Can you expose Goober’s target? [cristianbote/goober@`e3f99e9`/docs/docs/api/targets.md#L15](https://github.com/cristianbote/goober/blob/e3f99e960a59d606fe7d4584383834465883ec8d/docs/docs/api/targets.md#L15) Rather, is it possible to automatically detect and use React’s root instead?

I recently published 2 modules that might help you with this: https://github.com/fregante/webext-domain-permission-toggle https://github.com/fregante/webext-dynamic-content-scripts You'd just need: ```sh npm i webext-domain-permission-toggle webext-dynamic-content-scripts ``` ```js // in background.js import 'webext-dynamic-content-scripts'; import addDomainPermissionToggle...

This is best implemented by copying the native `` implementation that other GitHub buttons have. You can copy the whole **Filter** dropdown and also fix this other issue in one...

Releases are done via the actions tab, not by creating releases manually. The release and tag should be deleted and then done via the Release action.

Both stores may require you to update some details on the developer dashboard. Make sure there's a privacy policy on Google's dashboard and a verified email. As for the key,...

But that's strange, invalid grant means that the token is wrong, so yes, it's probably best to follow the guide again.

Once you follow the guide to update the Chrome token, please release a new version via the Actions tab as described. It'd be great to merge https://github.com/tanmayrajani/notifications-preview-github/pull/125 before then as...

> you might be getting emails too I guess Yes, AMO is really annoying. >I was wondering whether this is something that can be done via github action too Blocked...

We could also stop the request from happening unless the user is within the first 300px of scrolling. There's no point in fetching it if one can't even see it....

Thank you! I’ll make sure it works correctly soon