docs: clarify Events private preview availability - #363
Merged
Hauke Löffler (hloeffler) merged 3 commits intoSep 15, 2026
Merged
Conversation
Copilot started reviewing on behalf of
Hauke Löffler (hloeffler)
September 14, 2026 15:32
View session
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
A human must confirm whether private-preview documentation may be published.
Pull request overview
Adds a private-preview availability notice to the Events documentation.
Changes:
- Clarifies setup and enrollment requirements.
- Directs customers to their Customer Success Manager.
File summaries
| File | Description |
|---|---|
src/multiplayer-servers/monitoring/events.md |
Adds the availability notice. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Copilot started reviewing on behalf of
Hauke Löffler (hloeffler)
September 14, 2026 15:49
View session
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The notice omits two enrollment clarifications required by the PR goal.
Get a fresh assessment by requesting another Copilot review.
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Balanced
Hauke Löffler (hloeffler)
requested a review
from Christian Reinecke (antiphp)
September 14, 2026 15:50
Copilot started reviewing on behalf of
Hauke Löffler (hloeffler)
September 14, 2026 15:53
View session
Christian Reinecke (antiphp)
approved these changes
Sep 14, 2026
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The notice omits two setup and enrollment clarifications required by the PR description.
Review details
Suppressed comments (1)
src/multiplayer-servers/monitoring/events.md:4
- The availability notice omits two requirements promised in the PR description: initial setup by the GameFabric team is required, and configuring event permissions does not enroll an installation. Without these details, readers may interpret the Permissions section as sufficient to enable Events.
Events are currently available only to customers enrolled in the private preview. Contact your Customer Success Manager to request enrollment.
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Balanced
Hauke Löffler (hloeffler)
deleted the
docs/events-private-preview-availability
branch
September 15, 2026 07:52
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
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.
Goal of this PR
Clarify that Events are currently available only to customers enrolled in the private preview.
Add an availability notice explaining that:
How did I verify the changes?
yarn docs:buildpassed.git diff --checkpassed.Additional context
The Events documentation was added in #354 without a private-preview notice. The original review discussion states that the documentation was written with general availability in mind, while preview access may differ.
This change clarifies availability if the page is included in a documentation release. Reviewers should confirm whether private-preview documentation may be published at all. If not, a notice alone is insufficient and the page should be excluded from publication.