You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main branch in this repo has required status checks enabled to make sure that the Heroku deployment succeeds before allowing the PR to be merged. This works fine for PRs that are opened from a feature branch in this repo. However, when a PR is opened from a fork, the deployment_status workflow trigger errors out (here's an example).
As a result the status checks annoyingly get stuck as "waiting for status"
A while back, I tried to add a command to trigger a manual refresh (Add command to manually refresh Heroku status in PRs #503), but it doesn't work—the issue_comment workflow trigger doesn't have the necessary metadata to create an API request. With some more effort, it could probably be made to work, but it's not very high priority at this time
Find another way to update Heroku status (that doesn't rely on the deployment_status trigger)
Disable the status checks
Manually bypass status checks
Avoid making PRs from forks
The text was updated successfully, but these errors were encountered:
The
main
branch in this repo has required status checks enabled to make sure that the Heroku deployment succeeds before allowing the PR to be merged. This works fine for PRs that are opened from a feature branch in this repo. However, when a PR is opened from a fork, thedeployment_status
workflow trigger errors out (here's an example).As a result the status checks annoyingly get stuck as "waiting for status"
The workflow trigger error seems to be a bug with Github, for which I opened a ticket (please vote up if you can!)
Workarounds:
issue_comment
workflow trigger doesn't have the necessary metadata to create an API request. With some more effort, it could probably be made to work, but it's not very high priority at this timedeployment_status
trigger)The text was updated successfully, but these errors were encountered: