-
Notifications
You must be signed in to change notification settings - Fork 6
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
Counting the number of CompatHelper installations #56
Comments
We ignore it: PackageAnalyzer.jl/src/PackageAnalyzer.jl Lines 507 to 508 in a7c2b1d
😛 |
It would be pretty easy to modify PackageAnalyzer to answer (1). All the "analysis" takes places in PackageAnalyzer.jl/src/PackageAnalyzer.jl Lines 480 to 541 in a7c2b1d
Package struct with information gained by inspecting the repo. So we could add a compat_helper field to the struct and check if the workflow exists in that function, either by direct name or actually looping through workflow file contents and looking for the string "CompatHelper" or such. (I'd be in favor of such an addition since I think it's useful to know!)
For (2) and (3), I think that might be doable by combining the results of (1) with queries to the github api to check if an account is an org or not. I think that step might be outside the purview of PackageAnalyzer itself though. |
I think that in the future we may want to collect all filenames in |
I'm interested in answering the following questions for the packages in the General registry.
For the purpose of this analysis, let us define
package X has CompatHelper installed
ason the default branch of the Git repo for package X, there is a file named .github/workflows/CompatHelper.yml
. (I'm open to a better definition.)Would it be possible for me to use PackageAnalyzer.jl to help me answer these questions?
The text was updated successfully, but these errors were encountered: