fix: clarify what users should do if they don't have a TENANT_NAME #997
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
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
mjang
commented
Aug 20, 2025
mjang
force-pushed
the
fix-add-tenant-name
branch
from
c88aff8 to
16229d6
Compare
ADubhlaoich
approved these changes
Aug 20, 2025
travisamartin
approved these changes
Aug 20, 2025
Co-authored-by: Travis Martin <33876974+travisamartin@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Based on user feedback. After they read current docs, they couldn't figure out how to find their TENANT_NAME.
(IMO, it's already in the docs. But we can rewrite -- and add instructions if users can't find their TENANT_NAME.)
I've set up an "include" which includes the common content in these docs. (I've linked to the build for both). Suggestion for reviewers: make sure the sections that I've linked to (now) make sense:
Closes #995
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩