Repository navigation
chore: establish open-source repository foundation and CI - #1
Merged
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
Establishes the open-source repository foundation for SADA while keeping the project accurately documented as a documentation/architecture blueprint, not an implemented security product.
Included
Validation scope
The feature branch previously passed hosted CI and security workflows plus local repository, Markdown, pre-commit, actionlint, ShellCheck, and zizmor checks. This PR triggers validation against the actual pull-request event.
No application build, runtime test, database migration test, deployment, release, or application security audit is claimed: SADA application code does not exist yet.
Owner actions still required
The repository setup guide documents, but does not enable, branch protection/rulesets, required status checks, private vulnerability reporting, secret scanning/push protection, Dependabot alerts, dependency graph, and Actions default permissions.
Review note
The Code of Conduct is explicitly labelled as a concise adaptation based on Contributor Covenant 2.1, not the complete unmodified covenant text.