feat: ✨ add whitelist params to edit_branch_protection #200
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!200
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/200/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds push/merge/approvals whitelist params to
edit_branch_protectionso an admin can allow a specific user (e.g. a release bot likeop1st-gitops) to push to an otherwise locked branch.Params added
enable_push_whitelist/push_whitelist_usernamesenable_merge_whitelist/merge_whitelist_usernamesenable_approvals_whitelist/approvals_whitelist_usernamesUsername lists are comma-separated and replace the existing list. Each user must already be a write collaborator — the whitelist filters which writers may push, it does not grant access.
PATCH null-safety
Unpassed whitelist lists serialize as
null(leave-unchanged), never[](which would silently wipe an existing whitelist). Asserted byTestEditBranchProtectionFn_PushWhitelistRoundTrip.Docs
openspec/specs/branch-protection/branch-protection.demo.md).demos/README.md(new "Branch protection (governance)" section).Motivation: live config change earlier whitelisted
op1st-gitopsongoern/forgejo-mcpmain via the raw Forgejo API because the MCP tool lacked these params. This closes that gap.op1st Pipelines as Code/forgejo-mcp-code-scans-28mhv is running.
Starting Pipelinerun forgejo-mcp-code-scans-28mhv in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-28mhv -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-tmnth is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-tmnth in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-tmnth -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-lhcsg is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-lhcsg in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-lhcsg -fop1st Pipelines as Code/forgejo-mcp-code-scans-28mhv has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-tmnth has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-lhcsg has successfully validated your commit.
Task Statuses:
fetch-source
commit-title-check
build-and-test