chrnorm/deployment-status

Issues

• Update to use node 20

  #48 opened 9 months ago by bbergenroth
  4

• Note: If you want to show deployments in PRs / pull requests, pass `ref`

  #29 opened 3 years ago by tony
  4

• Question: Is it possible to change the name of a deployment?

  #47 opened 2 years ago by martisj
  0

• Too wide scope for deployments marked as inactive

  #45 opened 2 years ago by mateuszgorniak
  2

• `Error: fatal: repository 'https://github.com/XXX/XXX/' not found`

  #37 opened 2 years ago by ricardovanlaarhoven
  4

• Node.js 12 actions are deprecated

  #43 opened 2 years ago by selfagency
  1

• Resource not accessible by integration

  #31 opened 2 years ago by selfagency
  2

• Have you considered using `runs.post` to report the result?

  #38 opened 2 years ago by karfau
  1

• target_url mapping inconsistent with deployment-action

  #13 opened 3 years ago by nirvdrum
  4

• Add support for passing environment

  #22 opened 3 years ago by dhruvdutt
  1

• old deployments are not set as `inactive`

  #27 opened 3 years ago by spol-vt
  1

• `target_url` doesn't make it through to `deployment_status` events

  #25 opened 3 years ago by jimCresswell
  1

• Cannot update status of the `pull_request` workflow

  #12 opened 4 years ago by mxcl
  1

• Http validation failed on in_progress status

  #8 opened 5 years ago by sergeysova
  2

• environment_url not working

  #10 opened 5 years ago by benc-uk
  1