Bleeding Edge Updates
You have 3 options for receiving Better Grbl Support upgrades.
The typical means of receiving updates is through the (default) stable release channel. As upgrades make their way through the promotional model, the end state for production readiness is the stable channel.
Another option is to subscribe to the Release Candidate channel. The channel receives updates with more frequency than the stable channel, but poses some risk because not all (known) scenarios have been tested. While in an active development cycle, Release Candidates can be cut 1-7 times a week, depending on how quickly I'm moving features out.
Default Release Channels for receiving bgs updates (Octoprint Settings / Octoprint / Software Update):
The final option enables you to stay on top of all updates to bgs as they're being committed to the repo's development branch. The below procedure covers how to configure bgs to operate in this manner.
Please note this is not something for everyone. If you like a smooth and stable experience, possibly missing out on some cutting enhancements because they are not quite ready for distribution, this is not something for you.
Open up Octoprint Settings / Plugins / Better Grbl Support and select Subscribe to DEVEL branch. . . A restart of Octoprint is required for this change to take effect.
You will now receive update notifications from Octoprint whenever a commit is made to the origin development branch of bgs. All changes to code, once tested locally, are committed in this manner shortly after successful (initial) testing.
You can force an immediate update check by going into Octoprint Software Update, expanding Advanced Options, and clicking the Force check. . . button:
If at any time you want to revert to the stable (or release candidate) branch, go back to Better Grbl Support Settings, disable the Subscribe to DEVEL branch. . . checkbox, and restart Octoprint.