GitHub Dependabot organization secrets

Registry credentials for every repository in an organization, or only its private ones. The sync never changes which repositories reach a secret that already exists.

The connection

What	This provider
Vendor	GitHub
Key	`github-dependabot-org-secrets`
Availability	`available`. You can connect it today.
Credential penv holds	`github-token`
Values read back	no
Activation	`immediate`

What it moves

Direction	What it does
`export`	Writes names and values from penv into the store.

GitHub returns no value once it holds one, so penv can write here and cannot read back.

When a written value goes live

immediate. The running app sees a new value at once.

What happens to a name that exists

Direction	Policies you can pick
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

How you connect

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`token`	Access token	secret, masked here and sealed	yes	Needs admin:org. A repository-scoped token cannot reach the organization store.

What a mapping asks for

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`organization`	Organization	text	yes	no	The organization whose Dependabot store this environment maps onto.
`visibility`	Which repositories	choice	yes	yes	Private is the narrowest useful choice. All means every repository in the organization. One of Private and internal repositories, Every repository in the organization. Starts at `private`.

Permissions it needs

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`user:read`	every direction	yes	We cannot confirm which GitHub account this token belongs to.
`admin:org`	every direction	yes	Dependabot organization secrets need an organization admin token. A repository token cannot reach them.

GitHub Dependabot organization secrets

On this page