reload/GH Deployment from PlatformSH
Creating a GitHub deployment if PlatformSH has deployed
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Sep 2, 2025
- License
- None
Pinned Snippet
uses: reload/action-platformsh-gh-deployment@fab183e7dc8ba3be7d307395485625c5ceda2692 # no releases — HEAD as of 2026-07-11tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| PLATFORMSH_KEY | API key for connecting to Platform.sh | yes | — |
| PLATFORMSH_ID | ID for the Platform.sh project. | yes | — |
| GH_DEPLOYMENT_TOKEN | GitHub token, for deployment. E.g. github.token. | yes | — |
| PSH_DEPLOY_STATUS_PATH | The location of the deploy-status file on the website. | no | /sites/default/files/deploy-status |
| PSH_ACTIVITY_TYPES | Comma-seperated types of deployments to wait for. Default: push - See types here: https://docs.platform.sh/integrations/activity/reference.html#environment-activity-types | yes | push |
| PSH_DETECTION_WAIT | How long should we maximum wait for PSH to detect the push? If the branch doesnt exist in the PlatformSH GIT Remote, this is how long the action will take. Actually inactive environments get detected instantly. Default: 30 seconds. | no | 15 |
| BRANCH_NAME | Branch, which we will use to look | yes | — |
| USE_PULL_REQUESTS | If true, we will look up PSH environments based on PRs, rather than just the branch name. Default: 0 | no | 0 |
Outputs
| name | description |
|---|---|
| url | The ready-to-connect URL |
| deployment_id | The GH Deployment ID |
| deployment_status_id | The GH Deployment status ID |