Skip to content

chore: drop CODEOWNERS and use master as the default branch - #1

Closed
KFilippopolitis wants to merge 3 commits into
masterfrom
main
Closed

KFilippopolitis wants to merge 3 commits into
masterfrom
main

Conversation

@KFilippopolitis

Copy link
Copy Markdown
Contributor
  • Removes .github/CODEOWNERS. Only the maintainers have write access, so the ruleset's one required approval already comes from a maintainer; code-owner review added nothing.
  • The check workflow now runs on pushes to master (the new default branch), and the README says master and "maintainer's approval".

After merge: remove refs/heads/main from the main-protected-one-review ruleset's include list and delete the main branch.

🤖 Generated with Claude Code

KFilippopolitis and others added 3 commits October 13, 2026 12:54
Add the 8 example files (algorithm_examples.py, feres_analysis.ipynb,
ist_scenario_1..6 notebooks) unchanged from mip-jupyter 90c53c1, plus
README.md, .github/CODEOWNERS and the .github/workflows/check.yml
required check (allowed file types, cleared notebooks, no direct
network/shell/environment access).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 1 also rejects submodule gitlinks and only allows the check.yml
workflow. Step 2 requires nbformat 4, treats any non-null
execution_count as a failure, and rejects notebook-level
metadata.widgets. Step 3 now scans decoded notebook and script source
in Python (fails closed on errors) with more patterns and a rule for
lines starting with ! or % (except %matplotlib).

README states that CI is a tripwire, code-owner review is the gate,
and the notebook network policy and token scope are the runtime
control. The review checklist also covers text aimed at AI agents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Only the maintainers have write access, so one approval already comes from
a maintainer; code-owner review added nothing. The default branch is
renamed to master.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant