actions-marketplace-validations/Perforce Helix Core Actions
Run p4 commands within your GitHub Actions Workflows
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| command | p4 command to execute | yes | — |
| global_options | arguments for p4 cli that go before p4 command | no | — |
| arguments | arguments for p4 cli that go after p4 command | no | — |
| spec | This is the P4 spec contents for the resource you are creating | no | — |
| p4_version | Version of P4 binary to use. When a step has this set it will download and install the P4 CLI. | no | 21.2 |
| working_directory | The working directory to use when running p4 commands. | no | . |
Outputs
| name | description |
|---|---|
| stdout | Standard output from the p4 command |
| stderr | Standard error from the p4 command |
| exit_code | Exit code from p4 command |