[Bug][Module Name] Unable To Access Forked GHES repo (Similar to #4173)

[Bhoopalan1999]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

This issue is similar to #4173. Although it is marked as completed, I'm still unable to access forked GHES repositories via Devlake configuration.

What do you expect to happen

I'm expecting GHES and GHEC forked repos to be accessible via Github plugin in Devlake

How to reproduce

Steps to recreate:

1. I'm using Github enterprise.
2. While generating API token, I've given access to all sub categories and the main category for 'repo' - this is because I need access to private repositories also. Other access given are read:org, read:user
3. Private repositories can be successfully accessed
4. However, forked private repositories are not accessible
5. Forked public repositories are also not accessible. So issue is with all forked repos
6. Even when the account has access to the parent repo, the forked repo still couldn't be accessed.
7. Tried with 11 Forked repos - 2 Private and 9 Public - None of which could be connected. No problem with any other non-forked repository
8. I used my API token inside my custom script to hit Github api and fetch data from the forked repo. It works. So the token does have access to forked repos.

I think Github Enterprise Cloud is causing the problem. Because I tried to fork devlake-incubator repo from my personal account and tried to access it. It is working fine.

Anything else

Everytime

Version

v1.0.1@e061ef2

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[Bhoopalan1999]

I think Github Enterprise Cloud is causing the problem. Because I tried to fork devlake-incubator repo from my personal account and tried to access it. It is working fine. Updated the OP

[dosubot]

Hi @Bhoopalan1999! I'm Dosu and I’m helping the incubator-devlake team.

Based on the code, forked repo access in DevLake is controlled by the skip_forks parameter, not by whether you're using GHES or GHEC—there's no environment-specific logic for forks. If forked repos are missing, it's likely due to config, how the API response is handled, or a subtle bug in how forks are filtered or represented internally.

Could you confirm if skip_forks is set anywhere in your DevLake config or UI? Also, if you have any logs or error messages from DevLake when trying to connect to a forked repo, sharing those would help pinpoint where things are going wrong. Comparing the raw GitHub API response for a forked repo (using your working script) with what DevLake ingests could also reveal where the pipeline diverges. If you’re able to enable debug logging or add temporary log statements in collectRepos.go, that might clarify how forks are being handled at runtime.

Let me know what you find—this will help determine if a config tweak or a code patch is needed. For reference, the relevant fork-handling logic is described here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[Bhoopalan1999]

@dosu

We haven't done any config level customization. So I believe there's nothing as skip_forks anywhere. There are no errors. It just wouldn't populate the github repo in the connection - Like it doesn't have access to the repo but it does.

[dosubot]

Based on the code, forked repositories should appear in the UI if the backend receives them from the GitHub API—there’s no explicit filtering of forks unless skip_forks is set, and there’s no environment-specific logic for GHES/GHEC. Since your API token works in custom scripts but forks don’t show up in DevLake, the issue is likely in how the API response is handled or parsed in the backend, or possibly in how the UI displays the results.

To pinpoint the problem, try capturing the raw API response for forked repos using both your custom script and DevLake’s backend (enable debug logging or intercept the API call). Compare the responses to see if forks are missing or structured differently in DevLake’s output. If you find a discrepancy, focus on the repo listing and conversion logic in the backend, especially in collectRepos.go and repo_convertor.go (example). If the responses match but forks still don’t appear, check the frontend’s filtering logic in the repo selection UI.

If you’re willing to dig deeper or submit a PR, these are the best places to start. Let me know if you need pointers on enabling debug logging or tracing the API calls.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}