`CodeQL` default configuration for external-based forks

Open
#2,136 4 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd, security

Research direction

Start by comparing the default CodeQL setup behavior for internal-branch and external-fork pull requests, using the example PR linked in the issue. Confirm why the scan status is absent for the fork case and document or implement a way for required scans to run and report without customising the CodeQL action.

Written by the indexing model from the issue text.

Description

As recommended, I use the default setup for CodeQL. I also require the CI scans in my protected branches. However, whenever there is an external-fork-based PR, the scans are not run (= status is never reported). Example:

image

For internal-branch-based PRs it works smoothly, so it seems the default configuration doesn't work for external-fork-based PRs. Any advise on how to make this work without customising the CodeQL action yourself?

Dominant language
TypeScript
Stars
1.6k
Forks
493
Avg merge
1d 13h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/codeql-action

All issues in github/codeql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.