Skip to content
Discussion options

You must be logged in to vote

Thanks for the clarification — now I understand what you mean. But no, the file is correct as it is: a LICENSE file is always a verbatim, unmodified copy of the license text, and the unfilled brackets in the APPENDIX are part of that text. Let me break it down:

Why the LICENSE file is a verbatim copy

  • choosealicense.com puts it directly: "Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file."
  • GitHub's license detection relies on the file matching the canonical text — GitHub's own "Add license" flow creates exactly this file, unfilled brackets included, and projects like Kubernetes ship it the same way.
  • T…

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@d-biehl
Comment options

@BrunoC-L
Comment options

@d-biehl
Comment options

Answer selected by d-biehl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants