docs: clarify botstopper kubernetes instructions#1404
Merged
Xe merged 1 commit intoTecharoHQ:mainfrom Jan 15, 2026
Merged
Conversation
This makes it clear that when generating a kubernetes secret to pull the bot stopper image that: - no email is required - a user is required but the actual value of the username is not checked - the GH token needs to be pasted in Signed-off-by: Thomas Arrow <tarrow@users.noreply.github.com>
Contributor
|
Oh cool they finally fixed that? Sweet! Thanks for the PR! I'll merge ASAP. |
Xe
approved these changes
Jan 15, 2026
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
2 participants
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.
Purely a docs change:
This makes it clear that when generating a kubernetes secret to pull the bot stopper image that:
Checklist:
[Unreleased]section of docs/docs/CHANGELOG.md (N/A)npm run test:integration(unsupported on Windows, please use WSL) (N/A)