Uh oh!
There was an error while loading. Please reload this page.
Error sync if a private repo is not marked as private in team - #2269
Merged
Conversation
Kobzol
requested review from
Mark-Simulacrum, emilyalbini, jdno, marcoieni and ubiratansoares
as code ownersFebruary 26, 2026 10:14
Dry-run check results |
marcoieni
approved these changes
Feb 26, 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 freeto 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.
If a repository is private, we have to properly mark it as such in the
teamdatabase, because some bots can depend on this.Note that we cannot check this only in validation, because we could not distinguish private and missing repositories without a privileged auth token (a non-privileged one, such as the one in PR CI, would just see that the repo does not exist).