-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat: allow for exemption of repos from dependency graph integrator #1385
base: main
Are you sure you want to change the base?
Conversation
155b68a
to
8b71e13
Compare
8b71e13
to
07ce2f6
Compare
07ce2f6
to
92dc4d4
Compare
@@ -119,10 +121,27 @@ async function sendOneRepoToDepGraphIntegrator( | |||
} | |||
} | |||
|
|||
export function getReposWithoutWorkflows( | |||
export function repoIsExempted( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the language be passed in here? ie. 'Scala' or 'Kotlin'
const repoIsExcepted = exceptedCustomProperties.find( | ||
(property) => repo.id === property.repository_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the value of the property be compared to the language here? eg. is it Scala
value: 'Scala', | ||
}; | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we need another test for Kotlin and one for an entirely irrelevant language to prove that we distinguish
What does this change?
github_repositories_custom_properties
table.gu_dependency_graph_integrator_ignore
and excludes any repos that have this property from dependency graph integration.Why?
There is at least one repo that we know of that contains a script written in Scala file but that doesn't use sbt. As there are no dependencies for Scala in the repo, it doesn't need to have the sbt dependency submission workflow. Currently, the dependency graph integrator will identify this repo as requiring a workflow, and continue to raise a PR against it if the existing PR is closed or if the workflow is not merged in.
How has it been verified?
github_repositories_custom_properties
.