Add license check in validation steps
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No file, test, or entry point is named. First locate the quickstart's validation steps and determine whether license checking fits the project's scope and pipeline; done means an agreed check, supported license policy, and documented validation.
Written by the indexing model from the issue text.
Description
License checks can be very useful to add to pipelines -- they can prevent lots of expensive conversations with lawyers downstream.
Would it be possible to add some basic license checks to this quickstart project? Or does that not make sense for its scope?
- Dominant language
- Go
- Stars
- 51
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bazel-contrib/rules_go#4721 · 2 comments ·
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·
-
area/logging kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100