Add repository safety controls - #1
Merged
Merged
Conversation
Astroyimin
marked this pull request as ready for review
July 17, 2026 19:23
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
AGENTS.mdsafety and release rulesCODEOWNERSfor scientific and governance filesWhy
DAO uses separate private-development and public-release repositories. These controls reduce accidental public pushes, branch divergence, mutable release tags, unreviewed numerical changes, and generated-data leakage.
Validation
git diff --cached --checkCITATION.cffand workflow YAML parsing1.1.1,2026-07-18)make test_kernel_normcompilationThe complete Cloudy/HEASoft integration build was not run because the local Makefile still uses a placeholder Cloudy source path. The kernel normalization executable is a diagnostic and was compiled, not claimed as an accuracy pass.