Gitea Actions secrets

Actions secrets on a Gitea repository, written per secret and pruned per secret. Gitea never returns a secret's value.

Connection

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

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

Gitea 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 with write:repository. Gitea takes it with the token scheme rather than Bearer.

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

Field	Label	Kind	Required	Advanced	What it is
`host`	Server URL	text	yes	yes	Gitea, Codeberg or your own server. Must be reachable from the internet. Names starting with FORGEJO_ are skipped on every server, plain Gitea included. Starts at `https://gitea.com`.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`owner`	Owner	text	yes	no	The account or organization that owns the repository.
`repository`	Repository	text	yes	no	The repository this sync writes to.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`read:repository`	every direction	yes	Preview cannot list the repository's secrets.
`write:repository`	`export`	yes	Export cannot write anything.