Giters
chrnorm
/
deployment-status
GitHub action to create a deployment status update
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
77
Watchers:
1
Issues:
15
Forks:
49
chrnorm/deployment-status Issues
Update to use node 20
Closed
5 months ago
Comments count
4
Note: If you want to show deployments in PRs / pull requests, pass `ref`
Updated
6 months ago
Comments count
4
Question: Is it possible to change the name of a deployment?
Updated
a year ago
Too wide scope for deployments marked as inactive
Closed
2 years ago
Comments count
2
`Error: fatal: repository 'https://github.com/XXX/XXX/' not found`
Closed
2 years ago
Comments count
4
Node.js 12 actions are deprecated
Closed
2 years ago
Comments count
1
Resource not accessible by integration
Closed
2 years ago
Comments count
2
Have you considered using `runs.post` to report the result?
Closed
2 years ago
Comments count
1
target_url mapping inconsistent with deployment-action
Closed
2 years ago
Comments count
4
Add support for passing environment
Closed
2 years ago
Comments count
1
old deployments are not set as `inactive`
Closed
2 years ago
Comments count
1
`target_url` doesn't make it through to `deployment_status` events
Closed
2 years ago
Comments count
1
Cannot update status of the `pull_request` workflow
Closed
4 years ago
Comments count
1
Http validation failed on in_progress status
Closed
4 years ago
Comments count
2
environment_url not working
Closed
4 years ago
Comments count
1