CI: addlicense as linter
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
I think it would be a good idea to use [addlicense](https://github.com/google/addlicense) as linter in this project to ensure no copyright + license headers are missing. But I have identified the following issues to be resolved in order to use it for this:
- https://github.com/google/addlicense/issues/164
- https://github.com/google/addlicense/issues/162
- https://github.com/google/addlicense/issues/163
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.
Research direction
Start by reviewing the addlicense project and the three upstream issues linked in the report, then inspect this repository's CI configuration to find where a linter would fit. Done means the identified addlicense limitations are resolved or accounted for and CI reliably checks copyright and license headers.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100