Repository navigation
chore: repository hygiene and CI skeleton - #1
Merged
Merged
Conversation
🐕 Shuni ReviewNo new issues found. 🤖 Model: Review scope: Partial incremental re-review Reviewed new changes (2)
🐕 Review complete — View session on Shuni Portal 🐾 🤖 Model: |
|
| Topic | Details | ||||||
|---|---|---|---|---|---|---|---|
| Repository Governance | Establish contribution, security-reporting, ownership, pull request, and repository formatting conventions for safe collaboration.Modified files (6)
Latest Contributors(1)
| ||||||
| CI Security Gates | Add CI checks for commit and tree secret scanning, workflow linting and policy validation, with a strict CI Required aggregate gate and Renovate-managed pinned tools.Modified files (3)
Latest Contributors(1)
|
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.
What changed
The first step after the README: repository hygiene and a CI skeleton. No product code.
SECURITY.md: how to report a vulnerability privately.CONTRIBUTING.md: how changes land (small pull requests, Conventional Commits, squash merges, passing CI and one approval)..github/CODEOWNERSand a pull request template..gitleaks.tomland a CI job that scans every commit and the tree with a gitleaks binary pinned by version and checksum..github/workflows/ci.yml: secret scan, workflow linting (actionlint and zizmor) and one aggregateCI Requiredjob.renovate.json: keeps action commit pins and the pinned tool versions current..editorconfigand.gitignore.Why
mainis protected and everything arrives through small pull requests. These checks need to exist before the code does.How it was verified
Not in this pull request
Checklist