Prepare repository for public OSS release - #1
Merged
Conversation
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
Prepares
go-corefor a professional public OSS release by improving repository hygiene, onboarding documentation, security guidance, and public-facing project metadata.Changes
README.mdinto a concise public OSS onboarding guide.LICENSE.CONTRIBUTING.md.SECURITY.md..env.example..gitignorefor env files, local build/test outputs, editor noise, local certificates, and assistant-local artifacts..ai/prompt/context artifacts and duplicate context files..forge/andCLAUDE.mdfor Forge context workflow.Validation
go test ./...passed.go vet ./...passed.Notes
This PR intentionally does not rewrite git history. The scan did not indicate real credential leakage, and avoiding history rewrite preserves commit stability.