Document private repository feedback restrictions #3072
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.
Added documentation explaining that edit suggestions and raise issues feedback features are only available for public GitHub repositories. These features are now automatically disabled server-side when a repository is private to protect source code and internal documentation structure.
Files changed:
optimize/feedback.mdx- Added edit suggestions and raise issues to feedback types list with public repository requirement and warning calloutdeploy/github.mdx- Updated troubleshooting section to clarify that private repository restrictions are a security feature, not a configuration issueGenerated from [ENG-5753]: Do not allow enablement of issue feedback for private repositories @IHSten
Note
Low Risk
Documentation-only changes with no code or behavior modifications; main risk is user confusion if wording is inaccurate.
Overview
Documents that the GitHub-based feedback add-ons (
edit suggestionsandraise issues) are public-repo only and are automatically disabled for private repos for security.Updates GitHub deployment troubleshooting to treat private-repo disablement as expected behavior (with a warning callout), adds guidance to revalidate Git settings when a public repo can’t enable the toggles, and notes that switching a repo from public to private disables these features across all deployments (including previews).
Written by Cursor Bugbot for commit 27ad875. This will update automatically on new commits. Configure here.