Context
Baseline currently requires autoMergeAllowed: true in its default GitHub repository configuration. GitHub Free does not provide auto-merge for private organization repositories, so those consumers cannot satisfy the policy and must permanently skip the check.
Public repositories support auto-merge on GitHub Free. Paid private repositories can support it as well. This raises a broader question about whether Baseline should have additional policies for public repositories beyond the universal repository baseline.
Decision to make
Choose how Baseline should treat autoMergeAllowed:
- keep it in the default policy and require unsupported private repositories to declare an explicit
skip;
- stop checking the setting entirely;
- move it into an opt-in extra named after the capability, such as
auto-merge;
- move it into a broader extra for public repositories, which could later contain other public-repository settings.
The decision should clarify whether GitHub configuration extras represent individual capabilities or repository categories, while keeping the default policy useful for both public and private repositories.
Context
Baseline currently requires
autoMergeAllowed: truein its default GitHub repository configuration. GitHub Free does not provide auto-merge for private organization repositories, so those consumers cannot satisfy the policy and must permanently skip the check.Public repositories support auto-merge on GitHub Free. Paid private repositories can support it as well. This raises a broader question about whether Baseline should have additional policies for public repositories beyond the universal repository baseline.
Decision to make
Choose how Baseline should treat
autoMergeAllowed:skip;auto-merge;The decision should clarify whether GitHub configuration extras represent individual capabilities or repository categories, while keeping the default policy useful for both public and private repositories.