Based on the available documentation, the GitOps configuration for Permit.io currently supports SSH deploy keys for authentication (1) . The configuration requires creating an SSH key pair and adding it as a deploy key with write access to your repository (1) (2) . The JSON configuration structure shows the authentication type as SSH:

{
  "url": "<your-ssh-url>",
  "main_branch_name": "<your-default-branch>",
  "credentials": {
    "auth_type": "ssh",
    "username": "git",
    "private_key": "<your-private-key>"
  },
  "key": "<your-custom-id-string-without-spaces>"
}

(1) I don't have information in the available sources about GitHub App authentication as an alternative to SSH deploy keys for GitOps configuration. The documentation specifically covers the SSH deploy key method for GitHub, GitLab, and Bitbucket (1) (2) . If you need GitHub App authentication support, I'd recommend reaching out over Email to inquire about this feature or check if there are alternative authentication methods available.

To learn more, see the sources I considered: [[1] Git and Permit](https://docs.permit.io/integrations/gitops/github) [[2] Prerequisites Setup](https://docs.permit.io/how-to/deploy/on-prem/prerequisites)

Deploy Keys are disabled by default nowadays and requires Organisation Level settings change to allow them