GitHub-connected developer workflows
Public Check works from a URL. The full developer workspace needs a GitHub App install on a repo you own. Default access is read-only.
Developers who already live in pull requests and want Ready / Fix first / Do not launch on the change, not a second dashboard with no code.
Install the Invince GitHub App, pick one repository per project, sync. Launch gate comments on the pull request. Docs and findings follow the tree. Write access for opening PRs is off until you grant it.
The commit that moved health, security, or docs is in the same product as the signal. Invince still does not rewrite the repo unless you explicitly allow pull requests.
One repo per project
Same-repo only. That keeps another customer’s code out of your workspace and keeps your install scoped.
Launch gate
A check run and comment with a plain verdict. Use it as a required status if you want. You still own merge rules on GitHub.
Access
Read contents and metadata by default. Uninstall from GitHub at any time. Do not grant write access unless you want Invince to open pull requests.