47ng/Deploy to Clever Cloud
Deploy your application to Clever Cloud
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 4–6scored Jul 13, 2026
- Maintenance Recency
- Activelast commit Jul 8, 2026
- License
- MIT
Pinned Snippet
uses: 47ng/actions-clever-cloud@e4177599d4c6c9a552a6a4d998f94ba263578cd4 # v2.1.1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| alias | The alias of the application to deploy, if you are using a .clever.json file. | no | — |
| appID | The ID of your application (can be found in the Clever Cloud console). Takes precedence over `alias` if both are defined. | no | — |
| force | Use true if you want to force deploy even if it's not fast-forwardable | no | false |
| timeout | How long (in seconds) to wait at most before moving on. This can help saving build minutes with very long deployments, but you will lose any deployment failure information. | no | — |
| setEnv | Extra environment variables to set on the application before deployment. Values are separated by a newline character (\n), use a YAML literal block scalar `|` to preserve newlines and separate multiple variables definitions. (see https://github.com/47ng/actions-clever-cloud#extra-environment-variables) | no | — |
| deployPath | Specific directory to deploy instead of the entire project. Path must be relative to the repository root. | no | — |
| logFile | Path to a file where to store the deployment logs. | no | — |
| quiet | Don't print deployment output to the console. Use this in case your deployment may reveal secrets or PII. | no | false |
| sameCommitPolicy | What to do when local and remote commit are identical. Possible values: error, ignore, restart, rebuild. If not set, the Clever Cloud CLI default (error) will be used. | no | — |
Outputs
no outputs