Skip to content
quarry Check-in [8f527acdb5]
Login

Check-in [8f527acdb5]

Overview
Comment:Landed phase 4: the rule has a page, and the page says what it costs.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 8f527acdb503c38b15aff08ea364dd3b751180e4046794c8adffb5c3282a6fed
User & Date: ai-local on 2026-08-26 23:51:53.791
Other Links: manifest | tags
Context
2026-08-26
23:51
Landed phase 5: every row of the RFC's table, proved the way a person would do it. check-in: 763b776f6f user: ai-local tags: trunk
23:51
Landed phase 4: the rule has a page, and the page says what it costs. check-in: 8f527acdb5 user: ai-local tags: trunk
23:51
Landed phase 3: the merge is the fact, the reply is the claim, accept asks MayJoin. check-in: 2d30e99800 user: ai-local tags: trunk
23:16
RFC 0007 phase 4: the settings surface, under a

Protected branches beside capabilities on the repository settings page: a branch or glob per row, owners as logins, every matching rule applies, blank the owners to remove one. The form rebuilds the stored set, so a renamed row is a delete and a write.

The cost is stated where the rule is set, because both things it changes surprise someone who knows fossil: on this forge i means less than it means in fossil, and a stock client can be refused a push its capability string says it may make. Policy of this forge, outside the repository; a clone is byte-identical to an unprotected one.

The section is not drawn on a forge with no policy store. closed check-in: 0d3bcdd784 user: dmestas tags: protect-4

Changes