Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Not working with PR from fork
See original GitHub issuehttps://github.com/tibdex/backport/issues/33 recommends setting up this action job to work around the limitations of the GITHUB_TOKEN.
However, it seems like the same limitation applies to an app ID and client secret if it is injected via (organisation) secrets:
Secrets are not passed to workflows that are triggered by a pull request from a fork. Learn more.
So, how is this supposed to work exactly?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Allowing changes to a pull request branch created from a fork
Under the upstream repository name, click Pull requests. Issues and pull requests tab selection. In the list of pull requests, navigate to the...
Read more >Cannot trigger GitHub Actions while pull request from a fork repo
Finally, I found a setting called "Run workflows from fork pull requests". Enable it will solve the problem.
Read more >Pipelines for pull requests from forks | Bitbucket Cloud
For example, when I submit a PR from my fork here: https://bitbucket.org/pysph/pysph/pull-requests/259/. the pipeline build does not run.
Read more >Troubleshooting why pull requests are not triggering jobs on ...
If you revoked OAuth access to CircleCI on your VCS provider (GitHub, BitBucket) · If you're following the fork instead of the upstream...
Read more >Pull requests from forks does not trigger travis ci
The checks on the links are branch builds. For them to work, the PR author needs to set up Travis integration for their...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The issue is not intrisinc to
github-app-token. If you find a way to pass theapp_idandprivate_keywithout relying on secrets it will work.@tibdex Exactly, that’s what I wrote already. 😉
So technically none of this is supposed to work for repositories which are updated by forks? Then this should be written clearly in https://github.com/tibdex/github-app-token and https://github.com/tibdex/backport.