We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/jlewi/foyle/pulls
The "go test and build" workflow is stuck in the "golang test & build Expected — Waiting for status to be reported".
The docs say I should see an approval button but I don't. https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks#approving-workflow-runs-on-a-pull-request-from-a-public-fork
I think the issue could be that in my workflow. I trigger on push
foyle/.github/workflows/test-go.yaml
Line 3 in b4874f5
But not pull request. Since its coming from a fork there presumably isn't a push event to a branch in the repository.
The text was updated successfully, but these errors were encountered:
Trigger test-go on PR
0a9f663
* Right now the GHA doesn't trigger for PRs created from forks. * Update the GHA to trigger on pull_request Related to #282
Trigger test-go on PR (#283)
ecc579d
No branches or pull requests
https://github.com/jlewi/foyle/pulls
The "go test and build" workflow is stuck in the "golang test & build Expected — Waiting for status to be reported".
The docs say I should see an approval button but I don't.
https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/approving-workflow-runs-from-public-forks#approving-workflow-runs-on-a-pull-request-from-a-public-fork
I think the issue could be that in my workflow. I trigger on push
foyle/.github/workflows/test-go.yaml
Line 3 in b4874f5
But not pull request. Since its coming from a fork there presumably isn't a push event to a branch in the repository.
The text was updated successfully, but these errors were encountered: