Repository permission problems
A typed GitHub URL is not sufficient; the connected account must be able to resolve and read the repository and branch.
What this does
Explains authorization failures before source inspection.
What you need
The correct GitHub account and repository access.
What LaunchLayer automates
Repository lookup and permission verification.
What remains external
Organization SSO authorization and repository invitation acceptance.
Exact setup steps
Reconnect the intended account, authorize organization access if required, verify the branch, and inspect again.
How to verify it
The inspection shows repository permission verified and an exact commit SHA.
Common failures
Wrong account, private-repository denial, organization SSO restrictions, renamed repository, or missing branch.
Security considerations
Use least-privilege repository access and disconnect accounts no longer required.
Related articles
Real GitHub source builds; security and ownership.