feat(repos): add fast-forward-only and rebase-explicit merge flags and branch-protection cross-references #442

Merged

hexajon merged 2 commits from issue-431-432-repos-protection-and-merge-flags into main 2026-08-17 22:44:07 +00:00

Conversation 0 Commits 2 Files changed 10 +284 -163

hexajon commented 2026-08-17 22:08:11 +00:00

Owner

Copy link

Summary

#432: madt_repos edit and madtea repo edit gain allow_fast_forward_only_merge and allow_rebase_explicit, and the mislabeled allow_rebase_update description is corrected to its real meaning (update a PR branch by rebase). Fast-forward-only pairs with require_signed_commits, because it mints no merge commit and preserves the author identity. #431: branch protection is reachable in one hop - the madt_repos description and each tag_protect_* summary point to madt_branches_remote, and a new madt_help protection topic names its protect_* actions. Reference docs regenerated; the schema byte budget stays green.

Closes #431
Closes #432

## Summary #432: `madt_repos edit` and `madtea repo edit` gain `allow_fast_forward_only_merge` and `allow_rebase_explicit`, and the mislabeled `allow_rebase_update` description is corrected to its real meaning (update a PR branch by rebase). Fast-forward-only pairs with `require_signed_commits`, because it mints no merge commit and preserves the author identity. #431: branch protection is reachable in one hop - the `madt_repos` description and each `tag_protect_*` summary point to `madt_branches_remote`, and a new `madt_help` `protection` topic names its `protect_*` actions. Reference docs regenerated; the schema byte budget stays green. Closes #431 Closes #432

hexajon added 1 commit 2026-08-17 22:08:11 +00:00

feat(repos): add fast-forward-only and rebase-explicit merge flags; fix allow_rebase_update description; cross-reference branch protection (#431, #432) 273eae715c

hexajon scheduled this pull request to auto merge when all checks succeed 2026-08-17 22:08:17 +00:00

hexajon canceled auto merging this pull request when all checks succeed 2026-08-17 22:14:10 +00:00

hexajon added 1 commit 2026-08-17 22:26:52 +00:00

fix(repos): rename --allow-ff-only to --allow-rebase-update, matching the live forge field allow_rebase_update it sets c91b94cfbc

hexajon scheduled this pull request to auto merge when all checks succeed 2026-08-17 22:28:21 +00:00

hexajon force-pushed issue-431-432-repos-protection-and-merge-flags from c91b94cfbc to e6697e2b81 2026-08-17 22:29:19 +00:00 Compare

hexajon merged commit e6697e2b81 into main 2026-08-17 22:44:07 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

breaking

Breaking change - flag for release notes

  

bug

Something is not working

  

documentation

Documentation only

  

enhancement

New feature

  

epic

Tracking epic with dependency children

  

good first issue

Interested in contributing? Get started here.

  

help wanted

Maintainer would welcome outside help

  

refactoring

Code restructuring without behavior changes

  

resolution/duplicate

Closed as duplicate of another issue

  

resolution/invalid

Closed as invalid or not reproducible

  

resolution/wontfix

Closed as won't fix

  

security

Security issue or hardening

  

severity/critical

Security severity: critical

  

severity/high

Security severity: high

  

severity/low

Security severity: low

  

severity/medium

Security severity: medium

  

status/abandoned

Someone started, then walked away - up for grabs

  

status/blocked

Blocked by another issue or an external dependency

  

status/needs-decision

Waiting on a maintainer decision; workable once decided

  

status/needs-info

Waiting on reporter / more information before work can start

  

status/needs-verification

Done except verification in a live interactive session

  

testing

Test suite / CI infrastructure work

  

upstream

Related to an upstream repository, already reported there

No labels

breaking

bug

documentation

enhancement

epic

good first issue

help wanted

refactoring

resolution/duplicate

resolution/invalid

resolution/wontfix

security

severity/critical

severity/high

severity/low

severity/medium

status/abandoned

status/blocked

status/needs-decision

status/needs-info

status/needs-verification

testing

upstream

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sixfold-space/madtea!442

No description provided.