We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have varying state of repos that check license headers. Do a campaign that will add license checkers in every repo in the org.
We often merge features in various repos and I often have to comment that adding an ES license to new files is not needed for example.
Finding inconsistencies in license headers and fixing them manually.
Automation will ensure that all files in a repo have the right license headers, and ensure new code is checked in PRs for the same.
The text was updated successfully, but these errors were encountered:
+1 on automation of license headers.
It should generally be very straightforward ... a standard header for new files, or a specific exclusion if custom headers are needed.
Someone should address #98 authoritatively first, however.
Sorry, something went wrong.
No branches or pull requests
What/Why
What are you proposing?
We have varying state of repos that check license headers. Do a campaign that will add license checkers in every repo in the org.
What users have asked for this feature?
We often merge features in various repos and I often have to comment that adding an ES license to new files is not needed for example.
What problems are you trying to solve?
Finding inconsistencies in license headers and fixing them manually.
What is the developer experience going to be?
Automation will ensure that all files in a repo have the right license headers, and ensure new code is checked in PRs for the same.
The text was updated successfully, but these errors were encountered: