-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
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
[DevOps] GitHub Dependency graph does not work #4320
Comments
Will dummy files work or do we need the correct dependencies in these package.jsons? We could publish the generated ones. It would be yet another script to add to npm watch. @pavelfeldman |
I think the best would be if it would contain the real dependenciee too (like mirror them), then they will be shown too. I would see potential value in this and it seems easy to add. |
Would be good to know, maybe ask the folks at GitHub what the minimum requirement is to have the feature to work, I tried:
|
Opened a GitHub support ticket 928291 for it, try to get more requirements whats needed out of it. |
Relates #4320 The support suggest something like that. (does not close because we want to verify it works before)
Closed, the applied CR worked, see the outcome here: https://github.com/microsoft/playwright/network/dependents?package_id=UGFja2FnZS00MjQ2NjcwOQ%3D%3D |
Since we generate our package.json files for the main and sub-packages on-demand with a script, they are not in the repository.
It would be cool if we could create maybe a dummy folder with a minimal one for the packages, so that GitHub can pick it up and shows us a number and which projects are using it.
Example: https://github.com/playwright-community/jest-playwright/network/dependents?package_id=UGFja2FnZS04NjcyNjkyMjc%3D
@arjunattam
The text was updated successfully, but these errors were encountered: