Skip to content

Harden Merge and Automation Policy #4

Description

@FMCalisto

This issue tracks the remaining work needed to make the source template repository enforcement model consistent on GitHub.

Scope:

  • verify the baseline workflow set that should remain required on the source template
  • add required status checks to branch protection once the relevant workflows are present on main
  • review whether merge strategy defaults and branch rules match the intended maintainer workflow

Acceptance criteria:

  • the source template has a documented and enforceable merge path
  • required checks on main match workflows that actually run on the default branch
  • repository documentation reflects the final merge and automation policy

Validation expectations:

  • confirm the protection rules through the GitHub API or repository settings
  • verify that the required checks exist and report on pull requests as expected

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

highPriority: high priority issue.maintenanceType: maintenance of preserving the condition or the state.pendingStatus: pending awaiting decision or settlement.

Type

Projects

  • Status
    To do

Relationships

None yet

Development

No branches or pull requests

Issue actions