[Policy] Enable branch protection on main — PR-only workflow required

Open Beginner friendly
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
git, github
Domain
ci-cd, devops

Research direction

Start in GitHub Settings → Branches and review the branch protection options for the main pattern. Enable the listed pull-request, approval, and bypass restrictions, then confirm the PR-only policy is in place for the branches named in the issue.

Written by the indexing model from the issue text.

Description

policy security

Board Directive: PR-Only Workflow

The engineering team has adopted a mandatory PR-only policy effective immediately.

Required action for this repo:

  1. Enable branch protection on main:

    • Go to Settings → Branches → Add branch protection rule
    • Branch name pattern: main
    • ✅ Require a pull request before merging
    • ✅ Require approvals (at least 1)
    • ✅ Do not allow bypassing the above settings

  2. No direct pushes to main, master, or develop are allowed — all changes must go through a PR.

Why: The board has mandated that all code changes intended for distribution must be reviewed and approved before merging. This protects code quality and ensures accountability.

This issue was created by the engineering team as part of the org-wide policy rollout.

Dominant language
Makefile
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.