GitHub Enterprise Server Actions

Export secrets into Actions on your own GitHub Enterprise Server.

Connection

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

Direction	What it does
`export`	We write names and values from your environment into the store.

GitHub returns no value once it holds one, so we 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.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	Access token	secret; we mask it here and seal it	yes	A personal access token on your server with the repo scope.

You set these when you connect. Every mapping on the connection shares them.

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.

You answer these 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.

We probe for these when we verify 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.