LICENSE: start at MIT License so GitHub detects it - #32
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removes the two leading lines (
Azure SQL Developer Huband the blank line after it) soLICENSEbegins atMIT License. The text of the license itself is untouched.GitHub's license detection needs a close match against the canonical MIT text from the first line. The title above it made the file score as
NOASSERTION/ "Other", so the repository showed no MIT badge and would not appear in MIT-licensed searches. With the title gone it should resolve toMIT.This is a deliberate divergence from
microsoft/microsoft-sql, whoseLICENSEcarries the same kind of title line and is likewise detected asNOASSERTION. Matching that file exactly and getting the badge are mutually exclusive, and the badge was the preference here.Line endings, checked as asked
git diff HEAD~1 -w --statand the same command without-wproduce byte-identical output for the previous commit, so nothing in it was whitespace-only churn. Confirmed further:docs/DECISIONS.md,_config.yml,privacy.mdandLICENSEcontain zero CR bytes. History is LF, so there was nothing to restore.docs/DECISIONS.mdshows exactly one+line and no-lines. It only gained a line._config.ymlshows five+lines and no-lines.The
LF will be replaced by CRLFmessages git prints locally describe what a future checkout would write on Windows, not what was committed.Checks
npm testpasses, 38 files scanned. This change touches onlyLICENSE, which is excluded from Jekyll and not scanned by the house rules, so the build and link checks are unaffected.🤖 Generated with Claude Code