Repository navigation
Require repository bindings for project operations - #293
Merged
Merged
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
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.
Project operations now require a repository binding before contacting the provider. GitHub repository creation treats validation conflicts as unsuccessful creation; the existing project response retains
repo_url: nulland its VCS warning. Discovery omits unbound projects while valid bound-project behavior remains unchanged.Verification: 27 focused tests passed, including real API authentication and PostgreSQL persistence with synthetic GitHub HTTP responses. Coverage includes normalized names, organization and personal repository creation, OAuth/App paths, unavailable repositories, and successful bound-project discovery. Independent review completed without blocking findings. The committed quality gate passed with zero violations; the full suite and production rollout remain pending.