What Papaya can and can’t access
- Read the files and commit history of the repositories you select.
- Read basic details about those repositories, such as their names and branches. GitHub requires this for every app.
- Change your code, push commits, or open pull requests, unless you approve that separately.
- See issues, pull requests, Actions, or settings.
- See any private repository you don’t select.
You can change which repositories Papaya can read, or remove its access, at any time. See how to change or remove access.
Before you start
Your repositories need to be on GitHub.com.
If you use GitHub Enterprise Server, GitLab, or Bitbucket, contact us first.
The install is easiest for an organization owner.
If you’re not an owner, you can still start it, and GitHub will ask your owners to approve it.
Check for an IP allow list.
If your organization limits GitHub access by IP address, contact us before you install.
Install the app
Open the install page and sign in to GitHub if asked.
github.com/apps/papaya-code-analysis/installations/newPick the organization (or personal account) that owns your agent code.
Under Repository access, choose Only select repositories. Then pick the repositories that hold your agent code:
- Prompts
- Tool definitions
- Model settings
- The code that runs the agent
- Shared libraries your agents use
Check the permissions GitHub shows: Read access to code and metadata. Click Install.
If the button says Install & Request or Request, an owner has to approve the request first. We can start once they do.
Send us these details
After you install the app, we can see your organization and the repositories you selected. We only need two things from you:
- For each of your agents in Papaya, which repository holds its code. If one repository holds several projects, also tell us the folder.
- The branch that runs in production, if it isn’t the repository’s default branch.
How we use your code
- We read your code only to analyze your agents for you.
- We read the version of your code that matches your traces.
- Your improvements may include short excerpts of your code, such as the lines to change.
Questions?
Write to us, or reply to the email we sent you.