Skip to content

GItHub CI branch protection status check #308

Description

@ethanmusser

The current master branch protections rely on outdated status checks. These should be updated to instead require the new CI runs to succeed as status checks. To support this, the required CI matrix paths should be aggregated via a single CI status validation workflow.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions