Skip to content

LICENSE: start at MIT License so GitHub detects it - #32

Merged
Iqra Shaikh (Iqra617) merged 1 commit into
mainfrom
license-mit
Sep 25, 2026
Merged

Iqra Shaikh (Iqra617) merged 1 commit into
mainfrom
license-mit

Conversation

@Iqra617

Copy link
Copy Markdown
Member

Removes the two leading lines (Azure SQL Developer Hub and the blank line after it) so LICENSE begins at MIT 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 to MIT.

This is a deliberate divergence from microsoft/microsoft-sql, whose LICENSE carries the same kind of title line and is likewise detected as NOASSERTION. 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 --stat and the same command without -w produce byte-identical output for the previous commit, so nothing in it was whitespace-only churn. Confirmed further:

  • Committed blobs for docs/DECISIONS.md, _config.yml, privacy.md and LICENSE contain zero CR bytes. History is LF, so there was nothing to restore.
  • docs/DECISIONS.md shows exactly one + line and no - lines. It only gained a line.
  • _config.yml shows five + lines and no - lines.

The LF will be replaced by CRLF messages git prints locally describe what a future checkout would write on Windows, not what was committed.

Checks

npm test passes, 38 files scanned. This change touches only LICENSE, which is excluded from Jekyll and not scanned by the house rules, so the build and link checks are unaffected.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Iqra617
Iqra Shaikh (Iqra617) merged commit a3e73e4 into main Sep 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant