chore(license): add the fleet-canonical PolyForm Noncommercial license - #67
Merged
Conversation
This repo was missed by the fleet license rollout. The file is byte-identical to the LICENSE already committed on kanon and epistole.
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.
forkwright/.githubhas noLICENSEonmain. This adds the fleet-canonical PolyFormNoncommercial 1.0.0 file, byte-identical to the one already committed on
kanonandepistole(verified withcmpagainstorigin/main:LICENSEin each).Provenance
The file was sitting untracked in the local
projects/.githubcheckout — the only copy on thebox, in a checkout parked on an unrelated branch. Found during the metis cleanup campaign while
adjudicating that repo's branches. It reads as the fleet license rollout having reached this repo's
working tree and never been committed.
Verification
Content equality against two repos that already carry the file is the check that matters here, and
it passes. No build is involved.