Add support for setting or disabling custom TURNSERVER and SPRINKLER backends #109
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To support #98
goose now supports setting or disabling the custom backends via environment variables:
Disabling the turnserver means that the app is unable to tell whose turn it is to update a PR next, though they will continue to be displayed in the menu bar.
Disabling the sprinkler means Goose will be unable to receive real-time PR updates, instead relying on the 2-minute polling loop. This is already the default if the GitHub app isn't installed, so it won't change behavior for many/most people.