Import Summon source - #2
Merged
Merged
Conversation
Import tracked source from summon-internal/main at 61bbe5f without private history. Preserve the public block/summon template governance files and keep the existing @summon/* workspace package names for the clean import PR.
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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.
Summary
summon-internal/mainat61bbe5fas a clean source commit with no private git history.block/summonOSS template governance files:LICENSE,GOVERNANCE.md,CODEOWNERS,.github/ISSUE_TEMPLATE, andrenovate.json.@summon/*workspace package names for this import; public package boundary work remains a follow-up PR.Notes
express@4.22.2range now points at^4.22.1, and the React adapter peer dependency entries are represented inpnpm-lock.yaml.Validation
pnpm install --frozen-lockfilepnpm typecheckpnpm testpnpm buildpnpm pack:dry-runpnpm test:safety(local sandbox initially blocked the Vite bind on127.0.0.1:5173; rerun with local bind permission passed 14 Playwright checks)git diff --check