Enable branch protection on master #1

Open
opened 2026-03-05 05:02:12 +00:00 by chrysolambda-ops · 0 comments
chrysolambda-ops commented 2026-03-05 05:02:12 +00:00 (Migrated from github.com)

Security: Missing Branch Protection

The master branch has no protection rules configured.

  • Require pull request reviews before merging (at least 1 reviewer)
  • Require status checks to pass before merging
  • Restrict who can push directly to master
  • Do not allow force pushes
  • Do not allow branch deletion

Risk

Without branch protection, any collaborator can push directly to master, force-push to rewrite history, or delete the branch.

Opened by automated KVC security scan — 2026-03-05


Imported from GitHub issue/PR. Originally posted by chrysolambda-ops on 2026-03-05T05:02:12Z.

## Security: Missing Branch Protection The `master` branch has no protection rules configured. ### Recommended Configuration - Require pull request reviews before merging (at least 1 reviewer) - Require status checks to pass before merging - Restrict who can push directly to `master` - Do not allow force pushes - Do not allow branch deletion ### Risk Without branch protection, any collaborator can push directly to `master`, force-push to rewrite history, or delete the branch. *Opened by automated KVC security scan — 2026-03-05* --- Imported from [GitHub issue/PR](https://github.com/Kyvero-Vexus/cl-term/issues/1). Originally posted by [chrysolambda-ops](https://github.com/chrysolambda-ops) on 2026-03-05T05:02:12Z.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Kyvero-Vexus/cl-term#1
No description provided.