Skip to content

Protect master branch for website #76

@KirstieJane

Description

@KirstieJane

We're already hitting a few crossed wires with folks working on the same topic at the same time. Hopefully we can smooth that out in the long run, but for now I think we should definitely protect the master branch to require at least 1 review before PRs are merged.

What do folks think? What would be reasonable?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions