Skip to content
This repository was archived by the owner on Jul 16, 2025. It is now read-only.
This repository was archived by the owner on Jul 16, 2025. It is now read-only.

Branch protection on dev not adhering to best practices #281

@mapbox-github-ci-issues-4

Description

@mapbox-github-ci-issues-4

👋 Hey there! It's Changebot, and I help repositories follow our engineering best practices. My magic wand found some things I wanted to highlight for your review:

Item Current status Best practice guidelines
dev branch protection: Dismiss stale pull request approvals when new commits are pushed Unchecked Checked
dev branch protection: Require review from Code Owners Unchecked Checked
dev branch protection: Restrict who can dismiss pull request reviews Unchecked Checked
dev branch protection: Require status checks to pass before merging Unchecked Checked
dev branch protection: Restrict who can push to this branch Unchecked Checked

Can you take a look at these best practices and make any adjustments if needed?

Please tag @mapbox/security-and-compliance on this issue if you have any questions

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions