Ricky-Tigg
commented
8 months ago The repositories must be on GitHub. In the description of this product, there is no mention about the non-automation of the notification service when starting the browser. Instead, this task is devolved to the user, by manual intervention therefore; illustrative image:
Compared to the internal function called Watch of the GitHub web application, this extension is not only inferior to it in terms of the point described above, but also does not appear to compensate for this inferiority with a service that this Watch does not already offer. Sufficient justification to close.
For information, the reliability of the extension's service can be noted as poor since the notification is No updates available. No update available; is this really so?. Instead, see how this Watch, which does its job correctly, sends a notification each time there is a new version release.
P.S. This is one of the rare cases where I was able to conclude that an attempt at correction is not worth it.
v.: 0.2.0. Extension installed via
chrome://flags/; presence visible inchrome://extensions/. Relevant information forchrome://version/:Hello. Since the above mentionned installation, as attested by https://github.com/ungoogled-software/ungoogled-chromium/releases, a new version has been released. However, no notification is exhibited in this regard by this extension. Same observation while the default repository claudiodekker/ungoogled-chromium-macos is changed to ungoogled-software/ungoogled-chromium-windows. At the path
chrome://settings/content/siteDetails?site=chrome-extensionfor this extension, the web-permission for Notifications is Ask (default).Also noticeable, the option whose description is "The repository used to check for new release builds." must have an incomplete description because unknown is the platform on which the repositories available for selection reside. Could it be GitHub, as one might reasonably assume?