chore(branch-protection): allow actions + moko-deploy bots on protected branches #334

Merged

jmiller merged 1 commits from chore/branch-protection-bot-allowlist into main 2026-07-04 23:23:07 +00:00

Conversation 0 Commits 1 Files Changed 1

+18 -11

jmiller commented 2026-07-04 23:22:17 +00:00

Owner

Copy Link

Copy Source

Canonical copy of the org branch-protection provisioner. Adds the automation identities to the rule definitions so release automation can operate on protected branches:

• all rules: push_whitelist_actions_user: true + moko-deploy in push_whitelist_usernames
• dev, rc: enable force-push for the bots (enable_force_push, force_push_allowlist_usernames: [jmiller, moko-deploy], force_push_allowlist_actions_user: true) → dev can be reset to main via a single git push --force origin main:dev (delete+recreate can't work on a protected branch)
• main: force-push stays disabled

Because this provisioner POST-creates rules (not PATCH), it should set push_whitelist_actions_user correctly (the PATCH path silently no-ops — see mcp-mokogitea-api#30).

⚠️ moko-deploy needs org-team write access before it takes effect (mcp-mokogitea-api#30). Unblocks the dev-sync + version-persist fixes in Template-Generic#53. Applied identically to Template-Generic and Template-Joomla.

Canonical copy of the org branch-protection provisioner. Adds the automation identities to the rule definitions so release automation can operate on protected branches: - **all rules**: `push_whitelist_actions_user: true` + `moko-deploy` in `push_whitelist_usernames` - **dev, rc**: enable force-push for the bots (`enable_force_push`, `force_push_allowlist_usernames: [jmiller, moko-deploy]`, `force_push_allowlist_actions_user: true`) → dev can be reset to main via a single `git push --force origin main:dev` (delete+recreate can't work on a protected branch) - **main**: force-push stays disabled Because this provisioner **POST-creates** rules (not PATCH), it should set `push_whitelist_actions_user` correctly (the PATCH path silently no-ops — see mcp-mokogitea-api#30). ⚠️ `moko-deploy` needs org-team **write** access before it takes effect (mcp-mokogitea-api#30). Unblocks the dev-sync + version-persist fixes in Template-Generic#53. Applied identically to Template-Generic and Template-Joomla.

jmiller added 1 commit 2026-07-04 23:22:18 +00:00

chore(branch-protection): allow actions + moko-deploy bots on protected branches ... e99881ad65

Adds the automation identities to the branch-protection rule definitions so
release automation can operate on protected branches:
- all rules: push_whitelist_actions_user=true + moko-deploy in push whitelist
- dev, rc: enable force-push for the bots so dev can be reset to main via a
  single `git push --force origin main:dev` (delete+recreate cannot work on a
  protected branch)
- main keeps force-push disabled

moko-deploy needs org-team write access to take effect (mcp-mokogitea-api#30).
Unblocks the dev-sync + version-persist fixes (Template-Generic#53).

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

jmiller merged commit b885f12ece into main 2026-07-04 23:23:07 +00:00

jmiller deleted branch chore/branch-protection-bot-allowlist 2026-07-04 23:23:10 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

automation

Automated processes or scripts

breaking-change

Breaking API or functionality change

build

Build system changes

ci-cd

CI/CD pipeline changes

config

Configuration file changes

css

CSS/styling changes

dependencies

Dependency updates

deploy-failure

Automated deploy failure tracking

docker

Docker configuration changes

documentation

Documentation changes

dolibarr

Dolibarr module or extension

generic

Generic project or library

good first issue

Good for newcomers

health-check

Repository health check results

health: excellent

Health score 90-100

health: fair

Health score 50-69

health: good

Health score 70-89

health: poor

Health score below 50

help wanted

Extra attention needed

html

HTML template changes

javascript

JavaScript code changes

joomla

Joomla extension or component

mokostandards

MokoStandards compliance

needs-review

Awaiting code review

php

PHP code changes

push-failure

File push failure requiring attention

python

Python code changes

security

Security-related changes

size/l

Large change (101-300 lines)

size/m

Medium change (31-100 lines)

size/s

Small change (11-30 lines)

size/xl

Extra large change (301-1000 lines)

size/xs

Extra small change (1-10 lines)

size/xxl

Extremely large change (1000+ lines)

standards-drift

Repository drifted from MokoStandards

standards-update

MokoStandards sync update

sync-failure

Bulk sync failure requiring attention

sync-report

Bulk sync run report

template-validation-failure

Template workflow validation failure

tests

Test suite changes

type: bug

Something isn't working

type: chore

Maintenance tasks

type: enhancement

Enhancement to existing feature

type: feature

New feature or request

type: refactor

Code refactoring

type: version

Version-related change

typescript

TypeScript code changes

version

Version bump or release

version-drift

Version mismatch detected

work-in-progress

Work in progress, not ready for merge

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No labels

Priority -

Type -

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoCLI#334