Skip to content

document PR merge process #10

@wileyj

Description

@wileyj

this needs to be documented to prevent PR's from merging that break things.
i.e. if a change is made to how the tests archives are built, maybe require a succesful workflow using that updated composite action.

other things to consider: how many approvals should be required? protected branches?
etc.

Metadata

Metadata

Assignees

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