Skip to content

Main (and v1) Branch Protection Rules and PR enforcement #712

Open
@csviri

Description

@csviri

Currently the main branch is not protected, so users with write access can directly push to main and v1. We could enforce to have PRs always (what we anyway do now), but the release action would not be able to do pom.xml version updates directly neither. This is one issue to solve / discuss.

The other part to discuss below this issue is it would be an idea to force approvals from code owners, since this is relatively small team it would not be convenient (think holidays), but with 1 required code owner approval for all PRs could work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    github_actionsPull requests that update Github_actions codeneeds-discussionIssue needs to be discussed more before working on it

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions