You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
Currently it seems that the license header looks for two year validation Line of code. The Start Year and the Current Year, is this behavior the mandatory? or is there a reason to be so? I am asking because every time it runs the validation sometimes it breaks only because the current year is not found, it requires changes on the Header of older files which have already been validated in later commits.
A second issue would be the name of the configuration file config.json
hey @hectorcustodiozup after see the issue i think it can not be mandatory as a lot of projects do not use this as pattern.We will talk in the next week about that and return some options so we can discuss with you. Thanks for the contribution
About the configuration file, i agree that is not very intuitive. Do you think that license.json is a better name? or that the user could specify the config file?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently it seems that the license header looks for two year validation Line of code. The
Start Year
and theCurrent Year
, is this behavior the mandatory? or is there a reason to be so? I am asking because every time it runs the validation sometimes it breaks only because the current year is not found, it requires changes on the Header of older files which have already been validated in later commits.A second issue would be the name of the configuration file
config.json
header-license-checker/main.js
Line 22 in 635176f
The text was updated successfully, but these errors were encountered: