Add a license file to the repository

[echoix]

The tekton-lint npm package seems to have an "Apache-2.0" license in NPM, since it is specified in the package.json.
However, it would make it even more clearer to have a LICENSE file in the repository, so the GitHub interface could show the license and could also be returned by the GitHub API.

It is trivial to add a license on GitHub. The easiest way is through the web interface: Go to "Add file" then "Create new file", enter LICENSE as the file name, then a new button appears with "Choose a license template". Select the Apache 2.0, and finish up and commit. I added my own screenshots below, but some help is also available in the GitHub docs here:
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository

I could make a pull request too, but I think it's more appropriate to have it committed by the owners or maintainers.

Thanks!

---

1. 
2. 
3. 
4. 

[mbwhite]

Thank you - there is a LICENSE file in the repository

[echoix]

Nice! Will the latest release be available on npm soon?

[mbwhite]

Thanks @echoix

Problem is the publish was done by the personal account of the former maintainer. They have since left IBM.. so bit stuck.

I've added the tags file to a release.

[echoix]

Is there an organization account available for publishing, or any account that would administer this project?

@madbence Kindly, would you be willing to take the time to look at this and transfer the package, if you agree ?https://docs.npmjs.com/transferring-a-package-from-a-user-account-to-another-user-account?

For the moment, the version of tekton-lint contained in Megalinter wasn't able to be automatically updated. (I'm a maintainer of Megalinter :) ) https://github.com/oxsecurity/megalinter . Tekton-lint has been available since the beginning, as it was (and is still included in Super-Linter).

[mbwhite]

@echoix - there is a organization account and namespace @ibm that I've just been added to;
So I'll be able to publish an updated version there, and I think it would be preferred by the 'powers that be'

Is it bad I've not heard of Megalinter ? :-)

[mbwhite]

@echoix this has now been published under the @IBM namespace

npx @ibm/tekton-lint ./tekton-defns/**/*