GitHub Enterprise Server Actions

Export secrets into Actions on your own GitHub Enterprise Server.

The connection

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

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.

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

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

How syncs work says what each one does.

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	A personal access token on your server with the repo scope.

Fixed when you connect, and shared by every mapping on it.

Field	Label	Kind	Required	Advanced	What it is
`instanceUrl`	Server URL	text	yes	no	Must be reachable from the internet for us to write to it.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`repository`	Repository	text	yes	no	The repository this sync writes to.
`owner`	Account	text	yes	no	The account or organization that owns it.
`environment`	Environment	text	no	yes	Leave empty for the repository's own store. An environment must already exist.

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.
`secrets:write`	`export`	yes	Export cannot write anything.