Select Git revision
queries.sql.go
-
Jamie Tanna authored
As part of #282, it'd be useful to be able to provide policy requirements based on whether a given dependency has a license that isn't organisationally allowed. To future-proof this, we can make sure it's an array of `licences`, even though right now we only have a single entry. This requires we `left join`, in the case that there's no license found. Additionally, document how to use it. Closes #282.
Jamie Tanna authoredAs part of #282, it'd be useful to be able to provide policy requirements based on whether a given dependency has a license that isn't organisationally allowed. To future-proof this, we can make sure it's an array of `licences`, even though right now we only have a single entry. This requires we `left join`, in the case that there's no license found. Additionally, document how to use it. Closes #282.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.